← Prev in month ← Prev in thread
Next in thread → Next in month →

[OASIS Issue Tracker] Created: (EBXMLMSG-36) AS4 5.1.2(b)

From
OASIS Issues Tracker <>
Date
2013-10-12T13:13:33+00:00
ID
1453736657.22741381583679888.JavaMail.tomcat@customer-jira
Thread
[OASIS Issue Tracker] Created: (EBXMLMSG-36) AS4 5.1.2(b)
AS4 5.1.2(b)
------------

                 Key: EBXMLMSG-36
                 URL: http://tools.oasis-open.org/issues/browse/EBXMLMSG-36
             Project: OASIS ebXML Messaging Services TC
          Issue Type: Bug
          Components: AS4 Profile
            Reporter: Pim van der Eijk


This section states:

"This profile supports the One-Way/Pull MEP. When sending a Receipt for this MEP, a Receiving MSH conforming to this profile MAY bundle the Receipt with
any other ebMS message header (including an eb:PullRequest signal) or message body"

Bundling is about combining sub-element of eb:Messaging,  such as UserMessage and different types of SignalMessages.    It is not clear to me how a receipt could be bundled with a message body.

Perhaps what is meant is:

"This profile supports the One-Way/Pull MEP. When sending a Receipt for this MEP, a Receiving MSH conforming to this profile MAY bundle the SignalMessage containing the Receipt with
another SignalMessage including an eb:PullRequest signal or a UserMessage sent to the same MSH as the received message was pulled from."

Actually, it would be useful to constrain this further to the first option (bundling with a pull request),  and specifically to bundling the receipt with an pullrequest addressing the same MPC as the pulled message was pulled from. 
    



-- 
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
← Prev in month ← Prev in thread
Next in thread → Next in month →