|Subject:||An Usefull Fix :: Fwd: Kandula interop sample - run transaction manger from service|
|Date:||Thu, 15 Sep 2005 17:50:02 +0600|
Forwarding to the Dev list....
Important issue regarding handler depleyment and threads...
I think we should add a note to the documentation with this issue, Advising the users to deploy handlers using client-config....
---------- Forwarded message ----------
From: [email protected] <[email protected]>
Date: Sep 15, 2005 5:35 PM
Subject: RE: Kandula interop sample - run transaction manger from service
To: [email protected]
Exactly. Client GUI calls service which takes care about all the registering and transactionality. This service invites other services to take part in current activity. When finished, result of transaction is given back to the client.
Coz I am new to WS, JTA and Kandula as well I was trying to reuse existing sample. For the present I have solved the trouble (my handler runs on separate thread) by adding this handler to request flow in client-config.wsdd at axis instead of deploying it within invoked service. In this way my handler is called first - within the same thread.
But I'm still not sure if Kandula was intended to be used in this way.
have the same feeling but can't verify just now. If this is the case how can I handle the problem?
The above method
basically looks for the transaction in the thread and returns it to the
caller (handler ).
Kandula interop sample works fine… however what about when I need to start the whole transaction stuff not from the client but from the service?
Let's assume service (call it Initiator) that contains functionality of InteropPortTypeRPCServiceTestCase.java from the sample (starts transaction manager, activate and register within coordinator service). This service invokes InteropService (like in the sample) and if transactions handlers within these services are deployed correctly, coordination context from Initiator should be passed to InteropService in the message header and initiates registration within the same activity. My trouble is that
Transaction tx = tm.getTransaction() called from TransactionHandler while invoked refers to null. Where's the difference between interop sample and example described above?
Please correct me if the idea using transaction manager like in the sample is wrong or if there is more straightforward way how to get described functionality.
"May the SourcE be with u"
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: Kandula interop sample - run transaction manger from service, Thilina Gunarathne|
|Next by Date:||svn commit: r289226 - in /webservices/kandula/trunk/java: src/org/apache/kandula/context/at/ test/org/apache/kandula/context/ test/org/apache/kandula/coordinator/ test/org/apache/kandula/coordinator/context/, thilina|
|Previous by Thread:||re: ws-transaction, Thilina Gunarathne|
|Next by Thread:||svn commit: r289226 - in /webservices/kandula/trunk/java: src/org/apache/kandula/context/at/ test/org/apache/kandula/context/ test/org/apache/kandula/coordinator/ test/org/apache/kandula/coordinator/context/, thilina|
|Indexes:||[Date] [Thread] [Top] [All Lists]|