M�rcio Em�lio Cruz Vono de Azevedo wrote:
The solution is not actually correct in case you actually need to propagate the transaction context. (i.e. if from within methodA of the Bean A that lives on host A a call is made to methodB of Bean B that lives on host B and methodA is transactional (i.e. REQUIRES_NEW, REQUIRES) and method B just REQUIRES, then the solution will not be entirely correct, because methodA will run in its own transaction (txA)and method B will run in its own transaction (txB). According to the spec, txB should be subordinate to txA and commit/rollback when txA is committed/rolled back, while using the change suggested, txB will always commit even if txA is rolled back.Yes, you found the solution indeed!!! I've tried it and it solved my problem!!! Thank you very much!-- M�rcio Em�lio Cruz Vono de Azevedo System Specialist Inatel Competence Center http://www.inatel.br
Hope this is not too complicated :)
I assume that Tyrex stopped working as a DTM when client interceptors were introduced into JBoss (this is what I could figure out from the way client interceptors are written, it turns out they never ask Tyrex to serialize a transaction propagation context). I don't yet have a quick fix for this and according to David Jencks, 4.0 will have JBoss native TM run distributed txs, there also will be enough support in the interceptors/invokers/transport stuff to easily replug-in Tyrex. I guess, I can write a new plugin for 4.0 when the stuff David spoke about shall hit CVS.
Anatoly.
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
