Dasarath Weeratunge schrieb:
Hi Dasarath,
well first of all thanks so much for all your answers yesterday it
helped me alot. So I think I am getting closer to understand the
TxHandler.SO the TxHandler org.apache.kandula.geronimo.TxHandler is used
to extract the context from the soap message, pass it to a JTA
Transaction via bridging and bind this tx to the current thread, right?.
The other TxHandler org.apache.kandula.coordinator.at.TxHandler does
pretty much the same thing but uses the kandula transaction manager,
right? So for example if I have a j2ee web service I would use the
geronimo.TxHandler for incomming calls because of the JTA stuff and I
would use the other handler to add the context of the tx to the soap
message, right?
Yes.
We can also do this the other way as well. What if an EJB want's to call a
transactional .NET component?
-- Dasarath
So because of the testSuite1, I will work on that in a couple of days
unfortunately I am busy with my thesis stuff right now and won't have
the time to work on that for the next two weeks. After that I will be
more than glad to help.
THX
-Dominik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Mmh, my guess is that the EJB would use the TxHandler like the J2EE web
service I described and the .NET component would use the TxHandler
org.apache.kandula.coordinator.at.TxHandler for incoming and outgoing soap
messages, right? So in addition to the other case, when I have a non-J2EE
client I also would use the org.apache.kandula.coordinator.at.TxHandler for
incoming and outgoing messages, right?
thx
-Dominik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
