More from Tyrex integration front.
The deal is like this. JBoss TxInterceptor seems to assume that Transaction.commit() and Transaction.rollback() is equivalent to TransactionManager.commit() or TransactionManager.rollback() in that it will disassociate the current thread upon completion or rollback of the transaction. Judging from JTA javadoc documentation, only the TM says it will drop the tx association. Well, this is not true, at least in the context of Tyrex. I don't really care which interpretation of the JTA spec is correct. In any case, when I did the integration of Tyrex a while back, I put necessary changes to handle this. (see Annotated version of TxInterceptorCMT v 1.10 starting with line 363. Somewhere along the way (v 1.12) this got dropped. Can I reinstate that? Actually what is the reason we call commit() on transaction rather than on TransactionManager ? ------------------------------------------------------------------------- Anatoly Akkerman Computer Science Dept. Courant Institute of Mathematical Sciences, NYU 715 Broadway, #719 Tel: 212 998-3493 New York, NY 10003 Fax: 212 995-4123 ------------------------------------------------------------------------- _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
