Easy :-)
When the conversation management function above the MSH sets up a new
conversation, it must supply the necessary internal routing information to
the MSH along with the conversationId that goes in the message header. The
MSH has to keep both of them in its persistent store. The internal routing
information would be some kind of class name, applet name, or other
implementation thingie.
Regards,
Marty
*************************************************************************************
Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287; IBM tie line 863-7287
Notes address: Martin W Sachs/Watson/IBM
Internet address: mwsachs @ us.ibm.com
*************************************************************************************
David Fischer <david@drummondgroup.com> on 12/04/2001 11:45:24 AM
To: Martin W Sachs/Watson/IBM@IBMUS
cc: SHIMAMURA Masayoshi <shima.masa@jp.fujitsu.com>, Dan Weinreb
<dlw@exceloncorp.com>, ebxml-msg@lists.oasis-open.org
Subject: RE: [ebxml-msg] Re: Comments on the 1.09 about ConversationId
Routing on ConversationId? The ConversationId can be anything the sender
chooses. How can you route on ConversationId?
David.