mdsal-binding-util contains two important things:

1. TypedTransaction which is bound to a particular datastore
2. ManagedTransactionFactory which mimics how JTA works

The first item is really our preferred API: we no longer allow a transaction to span multiple LogicalDatastoreTypes anyway. Unfortunately DataBroker still has the API still pretends this something that is possible. Integrating these will provide the interaction model for DOM, allowing us to plot a migration path.

The second item is less important from API evolution perspective, but is important from user friendliness – developers familiar with JTA have real problem understanding the fundamental difference in OpenDaylight transaction model. Having these at their fingertips has the potential to make understanding things easier.

Split up and integrate mdsal-binding-util, so that TypedTransaction (perhaps as DatastoreTransaction?) is in mdsal.binding.api.datastore. The Datastore thing should be NMDA-enabled, i.e. use the generated identities from ietf-datastores.

The JTA thing will need to be evaluated, perhaps it should go to binding.api.datastore.managed, or the implementation should be part of mdsal-binding-dom-adapter?