On 20 Sep 00, at 13:22, Aaron Mulder wrote:
> So, the server code required to attach a new transaction to an
> old connection is fairly straightforward. But I don't believe we can
> determine *when to do that*. I don't believe that every DB connection
> that is not part of a transaction should be attached whenever a new
> transaction is started. Even if we tried to map connections to threads or
> something, I don't believe that every DB connection used in one particular
> place should be automatically attached to a transaction when a new
> transactions is started. Isn't the whole point of client/bean-demarcated
> transactions that the developer handles the mechanics of the transaction,
> so shouldn't they be the one to decide which connections go with which
> transactions?
Hi Aaron,
All resource manager accesses between the
UserTransaction.begin and UserTransaction.commit calls are part
of the transaction. In other words, if the user touches a new or
preexisting transaction (i.e. by executing a statement or prepared
statement) that connection must be enlisted in the transaction.
The user does not have flexibility in this regard.
-Dan
