Arvola,
The From party's implementation does know the collaboration role played by
the To party. It's in the CPA.
Since the association of delivery channels with service and action is
provided in the CPA, and since the endpoint address of the delivery channel
is also provided in the CPA, would it not be satisfactory for the
application to provide the To party's endpoint address as part of the "API"
information that goes with the request to send a message?
Yes, the sending MSH could also infer the receiving delivery channel from
Service and Action but to me it is cleaner to directly include the To
party's endoint address as API information associated with the message to
be sent.
(Again, I am working under the assumption that there is an unstated rule in
V 1.0 that each delivery channel must have a unique endpoint address. We
could add an additional disambiguator for version 2 if we want delivery
channels to share endpoint addresses.)
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
*************************************************************************************
Arvola Chan <arvola@tibco.com> on 08/21/2001 11:20:49 AM
To: Martin W Sachs/Watson/IBM@IBMUS
cc: "ebXML Messaging (E-mail)" <ebxml-msg@lists.oasis-open.org>,
ebxml-cppa@lists.oasis-open.org
Subject: Re: T2 SyncReply and ReliableMessagingMethod in
QualityOfServiceInfo
Marty:
>I suggest that V1.1 state that every delivery channel SHALL have a unique
>endpoint address (if V1.0 doesn't say so). For V2.0, we could consider
>permitting different delivery channls to share the same endpoint address
>and adding whatever disambiguator is required to make this work.
I agree with you that in order to allow the receiver to determine on which
delivery channel an incoming message has arrived, we need to either
assign unique endpoint addresses to delivery channels in 1.1 or add the
necessary disambiguator in 2.0.
My original question is how the sender MSH can select the appropriate
delivery channel, if it does not know the collaboration role played by the
receiver. Can the MSH infer the collaboration role from the Service/Action
elements or must it be told explicitly by the application the role played
by the receiver? In other words, how would the sender MSH go about
selecting the delivery channel (hence the endpoint address) given the
outbound ebXML message from the sender application.
Thanks,
-Arvola