[OASIS Issue Tracker] (EBXMLMSG-105) *.Initiator.* and *.Responder.* in PMode

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Pim van der Eijk created EBXMLMSG-105:
-----------------------------------------

             Summary: *.Initiator.* and *.Responder.* in PMode
                 Key: EBXMLMSG-105
                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-105
             Project: OASIS ebXML Messaging Services TC
          Issue Type: Bug
          Components: Core Spec
            Reporter: Pim van der Eijk


Section D.3.1 defines the PMode.Initiator.Party and PMode.Responder.Party and references back to section 2.2.3, where "Initiator" and "Responder" are said to apply to "channel-bound MEP".   

As explained in 2.2.5, in Push channels, it is the Sender that initiates. 
According to 2.2.6, in Pull channels it is the Receiver that initiates.

The definition of PMode.Iniator.Party in section D.3.1 says that "a user message initiating an MEP instance under this P-Mode must have its eb:Messaging/eb:UserMessage/eb:PartyInfo/eb:From element contain the same PartyId elements as the PartyId elements defined in this parameter." However, the "From" element identifies the Sender, so this can only be true for Push bindings.  

Similarly, the definition of PMode.Responder.Party says that "Any user message sent to the responder must have its eb:Messaging/eb:UserMessage/eb:PartyInfo/eb:To element contain the same PartyId elements as the PartyId elements defined in this parameter." 
However, the "To" element identifies the Receiver, so this can also only be true for Push bindings.  

For Two Way MEPs,  it should be clear that these parameters relate to the first leg.  
 




--
This message was sent by Atlassian JIRA
(v6.2.2#6258)