"adrian(a)jboss.org" wrote : Why?
Because I want to be notified that one of my buggily afterCompletions went wrong. ;-)
"adrian(a)jboss.org" wrote : It's valid for the JTA implementation to do:
|
| Psuedo code:
|
| | commit()
| | {
| | resources.end();
| | synchronizations.beforeCompletion();
| | resources.prepare();
| | log.writeResult(); // HERE we know/record the result of the commit (modulo
heuristics)
| | threadPool.submit(commitPhase);
| | removeThreadAssociation();
| | return;
| | }
| |
|
| so the rollback()/commit()/afterCompletion()s could be executed
| after the call to tm/tx.commit() has returned to you.
Shoot, the JTA spec is missing the Corba OTS 2.14.1.2:
"Corba OTS" wrote : Before doing so, however, it first issues after_completion
to any registered
| synchronizations and, after all responses are received, replies to the client.
"adrian(a)jboss.org" wrote : it would also be wrong to signal a transaction
failure, if it actually committed
| but one of the afterCompletions buggily threw an exception.
Yes, I agree. It would be nice if it had some facility to report warnings of such in a
different manner.
Ah well, such is life.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173890#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...