[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jta-dev] Rationale for preventing registration of a Synchronization in rollback only state?
|
I think it will be because after synchronization callbacks are not guaranteed to be called if the transaction rolls back - if the method was allowed it would give the wrong impression that it will get called.
Hello; what is the rationale for preventing the registration of a synchronization in a transaction/registry that has been marked for rollback?
(Does a transaction that is marked for rollback constitute an "
active transaction context"? I guess it must not here? What "active" means has been
discussed before; sometimes it does mean "active or marked for rollback" but not here apparently.)
I do understand the big picture, i.e. that a Transaction that is marked for rollback is doomed. But is there some actual harm I'm overlooking that registering a synchronization while the Transaction is in this state would incur?
Best,
Laird
jta-dev mailing list
jta-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jta-dev
-- Michael Musgrove
Transactions
