[jboss-dev-forums] [JBoss Transactions Development] - Re: Asynchronicity and transaction context propagation

[chtimi2]

anonymous wrote : 
  | I was thinking of the XATMI specification http://www.opengroup.org/pubs/catalog/c506.htm 
  | which defines how clients and servers interact in a DTP environment and the conditions under which the tx context is propagated. 
  | 
  | Section 3.5.2 says that if the client issues an asynchronous request and does not expect a reply  
  | then the request must not be issued in transaction mode. 
  | 
  | The client must gather up all replies to his outstanding service requests (the checked semantics refered to earlier in this forum thread) prior to commit. 
  |  
But the client does expect a reply: the requests wouldn't be one-way (even when void). 
To be more concrete by client i mean a Swing client that talks to a server (i feel that by client you mean the client of the RMs, which is our server?). 
Our application is typically only one AP server, which is a client of several  RMs if it can give some context. The RMs and the AP server (which is a client of the RMs) are co-localised (they live in the same VM).

I'm going to start thinking about a black-box unit test, to make sure we're talking about the same thing.


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255958#4255958

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4255958