[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (EBXMLMSG-22) Example Pull Message in spec is incorrect as it has a RefToMessageId
[ http://tools.oasis-open.org/issues/browse/EBXMLMSG-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Moberg updated EBXMLMSG-22: -------------------------------- It is true that the example is wrong in using a RefToMessageId that refers to a pull signal in the context of a One-Way/Pull MEP. However. in the context of a Two-way/Push then Pull MEP, the use of RefToMessageiD in the user's pulled message is ok to refer to the Pushed User message it relates to. > Example Pull Message in spec is incorrect as it has a RefToMessageId > -------------------------------------------------------------------- > > Key: EBXMLMSG-22 > URL: http://tools.oasis-open.org/issues/browse/EBXMLMSG-22 > Project: OASIS ebXML Messaging Services TC > Issue Type: Bug > Reporter: Pim van der Eijk > > See the discussion in: > https://lists.oasis-open.org/archives/ebxml-msg/201105/msg00033.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]