Hi All, Seasons Greetings :)
I've got a conversational service and it's client and it's all working great. However I'd like to extend this service to make a call to a non-SCA asynchronous application and I'm not sure as to how I should make the call back from the non-SCA application back into the SCA "world". Just to make sure this is all clear, the flow I'd like to achieve is: 1) Conversational client calls a SCA Service Operation. 2) SCA Service then makes a non-blocking call to the non-SCA operation. 3) non-SCA operation processes and notifies the originating Service conversation-instance of updates. 4) Any updates are returned to the original conversational client. Obviously the problem here is calling back into the originating conversation-instance from the non-sca application. Looking through the various specifications from osoa I can't see any suggested solutions to this, though I'm trying to ascertain if any of the following would work: o invoke a second client (such as a Servlet) and force the conversationID with no callback reference (to maintain the original client callback reference). o implement a second service through one component without callback and once again force the conversationID to hopefully find the originating service conversation-instance. Are either of these recommended solutions, or is there a more appropriate means of doing this? I'd like to find a solution that would continue to work between Tuscany releases. Any help would be greatly appreciated. Cheers, Dave. -- Dave Sowerby MEng MBCS --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
