>The calls from/to the completion iniatiator are asynchronous, so the >coordinator requires some message path back to the iniator - which is >not possible with non-WS applications.
Ok this is quite understandable. So the way I thought of running my app is to have a completionInitiator ws to inform my app about the outcome of the transaction. so by registering for the completion protocol I tell the coordinator the address of my completioninitiator for the callback which works great. But for some reason the completionInitiator is unable to deal with the callbackRegistry and wake up my waiting callback. So from my point of view this shouldn't have something to do with the WS because if I would have my the business Logic in a WS it wouldn't do something different to register a callback, right? I hope I didn't misunderstand so much again. thx -Dominik -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
