[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ebxml-msg] eb:RefToMessageId in one-way pull request responses
Hi Sander I’m not sure I understood your last paragraph on request-response. But in a business exchange, the party that “Pulls” the business data needs to be able to correlate the message with one that they sent out (our demo scenario #2 using one way Push & Pull). Don’t we need the refToMessageId in those cases ? ~Makesh From: ebxml-msg@lists.oasis-open.org [mailto:ebxml-msg@lists.oasis-open.org] On Behalf Of Sander Fieten Hi Theo, in One-Way MEPs, both Push and Pull, the eb:RefToMessageId is not relevant as the exchanged UserMessage is unrelated to earlier messages. If the UserMessage relates to an earlier message the MEP becomes a Two-Way MEP where the response must use the eb:RefToMessageId to indicate to which request it is the response to. So in a Two-Way/Push-and-Pull MEP the pulled message will contain a eb:RefToMessageId to the earlier pushed message. If the exchanged business documents also contain information about the request-response sequence then ebMS One-Way MEPs can be used to exchange the documents without loosing the request-response relation [on the level of the business apps]. Regards Sander On 19 Dec 2011, at 09:11, Theo Kramer wrote: The core spec, ebms-core-3.0-spec, shows clear examples of pull request responses containing an eb:RefToMessageId. However, in section 2.2.6 'The One-way/Pull MEP' states the following |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]