WS-AT and JTA

[slonko]

Can someone explain to me how WS-AT and JTA do fit together on implementation level?

The web service invocation follows the request/response paradigm. Whereas a JTA transaction is bound to a thread. Is the coordinator impl. supposed to keep the JTA context synchronously alive while listenting asynchronously to WS-AT events?


[Requester ] <--async--> [Coord.] <--sync--> [JTA Resource]


I picture this working when the transaction is relatively short lived, but does this work long running application transactions (i.e. WS-BusinessActivity)?

[starksm64]

http://www-128.ibm.com/developerworks/library/ws-transjta/

[slonko]

Ah, i didnt know that JTA supports suspend and resume of a transaction.
That means the coordinator doesnt need to keep the transaction alive, it can decide to suspend it when necessary.

But that means any subsequent request would be handled by a different thread. Does the jboss transaction manager support resuming of a tx by another thread?