As per my understanding if the TX were to be propagated across the AppServers we need to look at the JTS , can't we have the transaction propagated across varios AS's thorugh the JCA transaction inflow contract ?

JCA transaction inflow tackles only a small piece of the problem. It does nothing to help with outflow, wire format, or remoting of the transaction termination protocol. You could write all that stuff on top of the JTA, but you would wind up withing something that looked remarkably like the JTS, albeit without the interoperability benefits.

"jhalliday" wrote:JCA transaction inflow tackles only a small piece of the problem. It does nothing to help with outflow, wire format, or remoting of the transaction termination protocol. You could write all that stuff on top of the JTA, but you would wind up withing something that looked remarkably like the JTS, albeit without the interoperability benefits.

So does that mean the JTS implementation can be done using JCA tx inflow this would miss interoperability feature ? It looks portable and cleaner way of doing things to be , you have RA and you simply drop it in the JEE container and have the TX logic in the endpoints .

"jhalliday" wrote:I'm not sure how it's more protable, or indeed why you would want it to be portable when JTS already provides tx interop? What do you want to port it to and why?

I was thinking of the usecase when TX needs to be propagated across AS's , I know we do it using JTS . I was just trying to figure if we can do it using JCA as I have never used JTS , so was trying to escape from JTS ;) Moreover I guess JTS implementation is not completely in java , so was thinking of complete java stuff for TX propagation across AS's .