[OASIS Issue Tracker] (EBXMLMSG-22) Example Pull Message in spec is incorrect as it has a RefToMessageId

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

    [ https://issues.oasis-open.org/browse/EBXMLMSG-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59235#comment-59235 ] 

Theo Kramer commented on EBXMLMSG-22:
-------------------------------------

Further to this, section 5.1 'Selective Pulling' of part 2 of ebms V3 states the following

[Selective pulling] is only  intended to support the most common cases of message selection, e.g. selecting messages that belong to the same conversation (i.e. with same eb3:ConversationId value) or messages that are responses to some previous requests ( i.e. with a particular  eb3:RefToMessageId value).

and 

The selection semantics of such items is: messages from the targeted MPC will be pulled only if they contain a header element matching exactly the selection item.

This would indicate that a message to be pulled must contain a header element as follows

  <eb3:RefToMessageId>some_message_reference_id</eb3:RefToMessageId>

This conflicts with the following wording in 2.2.6 of the core spec

The second leg returns the pulled User Message unit. To conform to this MEP the pulled User Message unit MUST NOT include an eb:RefToMessageId element.

This is a conflict between the core spec and part 2 of ebms V3 and needs to be resolved.

> Example Pull Message in spec is incorrect as it has a RefToMessageId
> --------------------------------------------------------------------
>
>                 Key: EBXMLMSG-22
>                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-22
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Bug
>          Components: Core Spec
>            Reporter: Pim van der Eijk
>
> See the discussion in:
> https://lists.oasis-open.org/archives/ebxml-msg/201105/msg00033.html



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