[OASIS Issue Tracker] (EBXMLMSG-77) Inconsistency required MEPbindings minimal client

Bram Bakx created EBXMLMSG-77:
---------------------------------

             Summary: Inconsistency required MEPbindings minimal client
                 Key: EBXMLMSG-77
                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-77
             Project: OASIS ebXML Messaging Services TC
          Issue Type: Bug
          Components: AS4 Profile
            Reporter: Bram Bakx
            Priority: Minor


AS4 profile specifies in paragraph 2.3 the minimal client conformance profile.
In the feature set table (under 2.3.1) it lists that the "ebMS MEP" must support as initiating partner: One-way / Push and One-way / Pull.

In paragraph 2.3.3.1 (general P-Mode parameters) of this same comformance profile it is specified that "PMode.MEPbinding" requires only support for "http://www.oasis-open.org/committees/ebxml-msg/push"

"PMode.MEPbinding" should also support One-way Pull ergo "http://www.oasis-open.org/committees/ebxml-msg/pull" (as according to paragraph 2.3.1). 



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