I coded that a year and a half ago so I am working from memory |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.
?? where do you read that the interceptor makes assumptions about what needs to be associated with the TM when it leaves. Does the *EJB* spec say that the container shall dis-associate the thread going out? I sure don't remember that, If it is then show me. If it isn't why do you care, either way, I sure *don't* care if you keep the thread association or not, so feel free to put the code back. |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 ? The lack of care above :) marcf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
