Sorry for not getting back to u
> On Monday, March 22, 2004, at 11:30 AM, Dasarath Weeratunge
> > Hi all,
> > Will Geronimo be
using TyRex as its transaction manager?
> Definitely not.
What is the transaction manager that is in use at the moment in
that u plan to use? Can Geronimo use JOTM? (LGPL 2.1 or
I managed to get JOTM working with JOnAS 4.0. What I'm interested
in is the
interface between the transport layer interceptors and rest of the
This is the interface that Axis handlers will use. Different Impls
do different things here. We may also use
javax.jts.TransactionService/identifyORB and let the tm identify
sender/receiver callbacks to Axis.
> Can you please
explain how many vms are involved in your scenario and
> where the
transaction control resides? If you are running axis in a
> different vm
from Geronimo can you please explain why?
To my present understanding,
Axis and JOTM (or whatever JTS impl that will
needs to be in the
*same VM* so the association b/w thread and tx-context
Transaction control will be in the JTS impl. The basic idea is
for ws to ejb
calls, axis handlers to create wrapper objects that
respective web services and pass them to the JTS impl in place of
objects that it would have
got from the normal RMI transport. This way, the
domain where the
transaction originated (from ws or J2EE) will
transparent to the transaction manager. When an ejb makes a ws
exported remote objects handed over
to the transport layer by the
JTS impl will be wrapped using wrapper objects
again. In short we are writing
a new CRM using axis
and connecting that to the JTS impl. This CRM will
however *not be* JTS impl
From the perspective of jsr 109
impl, Axis *need not be* in the same VM as
we are using
the remote interface. This was proposed to keep the jsr 109
impl app server
Anyway, in the case Geronimo Axis will be in the same
> If you need to
> import transactions I suggest you
consider using the jca 1.5 mechanism
> using WorkManager/ExecutionContext
and XATerminator. This is already
> implemented and appears (with
limited unit testing) to work.
> Propagation of transactions between
vms is not yet implemented but
> will (IMO) make use of the networking
layer and the same transaction
> import facilities as the jca 1.5
The jca approach seems fine but we may have to take the
present ews remote
invocation code from the
wrapper web service and put it
in the Work object. Since jca supports jaas
anyway, it should not interfere
the security impl either.
However, there are two
1-Can we have axis and the resource adaptor running in the same VM?
we could pass the work object from
the wrapper web service to the
adaptor at run time.
2-Can we use the jca method for exporting transactions -
that is when ejbs
invoke web services?