|Subject:||Re: Kandula interop sample - run transaction manger from service|
|Date:||Thu, 15 Sep 2005 15:34:02 +0600|
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.....
On 9/15/05, michal.burian@xxxxxx <michal.burian@xxxxxx> wrote:
"May the SourcE be with u"
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Kandula interop sample - run transaction manger from service, michal.burian|
|Next by Date:||Re: WSBA implementations, Thilina Gunarathne|
|Previous by Thread:||Kandula interop sample - run transaction manger from service, michal.burian|
|Next by Thread:||Re: Kandula interop sample - run transaction manger from service, Thilina Gunarathne|
|Indexes:||[Date] [Thread] [Top] [All Lists]|