An Usefull Fix :: Fwd: Kandula interop sample - run transaction manger from service

[Thilina Gunarathne <cs...@gmail.com>]

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: michal.burian@bt.com <mi...@bt.com>
Date: Sep 15, 2005 5:35 PM
Subject: RE: Kandula interop sample - run transaction manger from service
To: csethil@gmail.com

 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.

 Best,

michal

  -----Original Message-----
*From:* Thilina Gunarathne [mailto:csethil@gmail.com] 
*Sent:* 15 September 2005 11:53
*To:* Burian,M,Michal,CXR7A C
*Cc:* kandula-dev@ws.apache.org
*Subject:* Re: Kandula interop sample - run transaction manger from service

 Hi,
Can u give some more details about ur scenerio, so that i can try to 
recreate the scenerion and check it. 
Also I'm bit confused about your usage too.
Are you trying to do all the registering and transactional service calling 
things inside a mothod in another service implementation. So that they'll 
execute when somebody calls the method.

Pls give me more clarifications. 

Thanks,
~Thilina

PS: I'm not the original author of Kandula1. My knowledge in the Kandula 
j2ee stuff is very poor. May be there is an alternative by using j2ee. 

 On 9/15/05, *michal.burian@bt.com* <mi...@bt.com> wrote: 
 
Hi Thilina, 

 have the same feeling but can't verify just now. If this is the case how 
can I handle the problem?

 regards

michal

 -----Original Message-----
*From:* Thilina Gunarathne [mailto:csethil@gmail.com] 
*Sent:* 15 September 2005 10:34
*To:* Burian,M,Michal,CXR7A C
*Cc:* kandula-dev@ws.apache.org
*Subject:* Re: Kandula interop sample - run transaction manger from service
 
 Hi Michal,
When somebody starts and registers for a activity, Kandula associates the 
trasaction to the executing thread (using a thread local variable). 

 tm.getTransaction()

The above method basically looks for the transaction in the thread and 
returns it to the caller (handler ).

I'm getting the feeling that this thread issue has to do something with your 
problem. just check whether the handler runs on a seperate thread.....

~Thilina

 On 9/15/05, *michal.burian@bt.com* <mi...@bt.com> wrote: 
 
Hello,

 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.

  Many thanks

Michal Burian

  


-- 
"May the SourcE be with u" 
http://www.bloglines.com/blog/thilina 
http://webservices.apache.org/~thilina/<http://webservices.apache.org/%7Ethilina/>
  



-- 
"May the SourcE be with u" 
http://www.bloglines.com/blog/thilina 
http://webservices.apache.org/~thilina/<http://webservices.apache.org/%7Ethilina/>
 

-- 
"May the SourcE be with u" 
http://www.bloglines.com/blog/thilina 
http://webservices.apache.org/~thilina/