Richard Monson-Haefel wrote:
>
> When passing a transactional context in a synchronized messaging environment
> like EJB, however, there is only one logical thread. In other words, the
> bean whose method was invoked (invokie) will not return until all the tasks
> are completed in that portion of the unit-of-work. If this is the case,
> there shouldn't be a problem passing the transactional context because the
> invoker thread will block until the invokie returns --making it impossible
> to commit before invokie completes its work. I'm assuming that the
> transactional context is used by the invokie to register itself with the
> same transactional manager and transactional context as the invoker.
>
That's exactly right. Tuxedo and other TMs check that the tx context going
in is the same as the one present when the method returns. This works
because the calling pattern is asynchronous. But there's nothing preventing
a CORBA/EJB implementation to get the transaction context, package it as an
attribute and send an asynchronous message (using JMS) where it is
unpacked. This is painful for the system to track.
-Sriram
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
