OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: update for section 2.4.5 of multi-hop

 Proposed update for section 2.4.5 of multi-hop:

Compliance with the SOAP Processing Model

In the SOAP processing model for intermediaries, any header that is understood and processed may be reinserted in the message before forwarding. The primary requirement for ebMS intermediaries is that they MUST NOT break the signature of messages they forward. This implies that these intermediaries do not alter in any way the ebMS related headers (eb:Messaging, wsse:Security, Reliability headers and WS-Addressing headers), when forwarding.

The eb:Messaging header MUST be understood by ebMS intermediaries in addition to ebMS endpoints (its @mustUnderstand attribute must be set to 1 or "true", as required in  [EBMS3CORE]).

By default all nodes in the multi-hop path act in the “next” role (http://www.w3.org/2003/05/soap-envelope/role/next).   However, ebMS intermediaries and endpoints MUST also act in the role of "nextMSH", which requires processing the eb:Messaging header for routing purpose. (role =   http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/part2/200811/nextmsh)

When using SOAP 1.2,  sending enpoint MSH MAY insert a @role attribute with the nextMSH URI above. Whether this role value is expected to be set is however a matter of agreement between endpoints (P-Mode).


- jacques

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]