[ https://issues.oasis-open.org/browse/EBXMLMSG-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54540#comment-54540 ]
Pim van der Eijk commented on EBXMLMSG-48:
------------------------------------------
See also https://issues.oasis-open.org/browse/EBXMLMSG-68.
PMode lookups for incoming messages without PModeID attribute or without AgreementRef element could be contrained to PModes that don't have them.
> P-Mode search recommendation
> ----------------------------
>
> Key: EBXMLMSG-48
> URL: https://issues.oasis-open.org/browse/EBXMLMSG-48
> Project: OASIS ebXML Messaging Services TC
> Issue Type: Improvement
> Components: Core Spec
> Reporter: Theo Kramer
>
> P-Mode search is not defined and different systems may behave differently
> As an example P-Modes may be identified in multiple ways. Eg.
> 1 Using the @pmode in the agreementref - although optional this imo is the most simple approach
> 2 combination of to/from/service/action - this would fail on mismatch and would return EBMS:0010.
> 3 combination of to/from/agreementref - ditto
> 4 Just agreementref
> 5 combination of from/MPC for pulls
> and finally
> 6 just MPC for pulls
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
