DataModels & Transactions
This is kind of a carry-over from the "approaching datamodels" thread. The community mentioned the need for transactions in the DataModel/Binding API, and this thread is intended to address that issue.
Does anybody out there have any experience in the javax.transaction package? I'm wondering if we couldn't leverage the work already done there for transactions. From my initial readings on the subject, it looks like we could use javax.transaction.UserTransaction (I think?).
In simple applications transactions would live only within the current VM. We would therefore need a simple TransactionManager implementation that manages transactions within the context of a single VM. This should be doable, I think.
For complex applications such as those requiring distributed transactions, we could use a remote TransactionManager (for example, an application server) instead.
The thing I'm interested in the most is that the semantics and API for using transactions should be the same regardless of whether a simple transaction scheme is used or a complex distributed transaction scheme. I'm wondering if we can avoid reinventing the wheel by using javax.transaction stuff.