Sure but it wasn't really a problem of the code so it was more a problem of basic understanding I guess. So what I've tried to do is to start a TX with a non web service app, using the callbackRegistry to make the completionInitiator tell the app the outcome of the transaction. but because the completionInitiator is a WS and the app is not they apparently have different instances of the callbackRegistry which makes it hard for the completionInitiator to communicate with the app and to wake up the waiting thread. Ok so I hope I got it right this time by not mixing up so much stuff.
thx -Dominik -------- Original-Nachricht -------- > Datum: Tue, 16 Oct 2007 17:49:06 +0200 > Von: Hannes Erven <[EMAIL PROTECTED]> > An: Dominik Heller <[EMAIL PROTECTED]> > CC: [email protected] > Betreff: Re: Help for Kandula 1 > Hi Dominik, > > > > Ok Never Mind I've found the problem. > > Can you please share with us what the problem was and how you managed to > fix it? > > > Thank you very much, > > -hannes > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kanns mit allen: http://www.gmx.net/de/go/multimessenger --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
