Can I refer you to the specifications. You will need to read them if you are
attempting to bypass the spec defined assumptions/behaviours.
You will find lots to read :-)
I will also repeat, your question is also off topic for the JMS forum.
The basics are:
JTA - java mapping of XA/Open desc
Yes, I agree with you that my question has little to do with JMS. And I was
just trying to use it as an example to find out what need to be done if I want
a distributed transaction span over two asynchronously invoked
services/components.
The most important point you made (and thanks for bring
Your question has little to do with JMS (other than you are sending a TPC in a
JMS message).
What you are doing might be made to work, but there are many other
considerations
you haven't taken into account (at least from the information on your post).
e.g.
1) A JTA transaction cannot be activel
Hi Adrian,
Thanks for you information. It is understood that: Transaction propagation
context will not be transfered through messages like Session Bean and Stateless
Bean do;
But we have a scneario that to make two asynchorously responded services in one
transaction. That's the reason we do
Besides MySQL doesn't even support XA.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862492#3862492
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862492
---
The SF
No. And it is deliberatly designed/speced that way.
Otherwise it wouldn't be asynchronous.
A sender and receiver's tranasctions are quite independent and may be separated
both spatially and temporily.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862491#38624
