[OASIS Issue Tracker] (EBXMLMSG-47) MSH behaviour if TO/FROM is not recognised

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/EBXMLMSG-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52573#comment-52573 ] 

Sander Fieten commented on EBXMLMSG-47:
---------------------------------------

What do you mean by recognised on a receiving MSH? 

Is this the case when the ebMS header does contain To and From information and the message can be matched to a P-Mode, but that the values P-Mode defines for these elements (through the Initiator and Responder parameter groups) do not match the ones in the message header?

In that case I would think that an EBMS:0003 (ValueInconsistent) must be returned because "some element/attribute value is inconsistent either with the content of other element/attribute, or with the processing mode of the MSH,"

If To or From information is missing from the header I expect an EBMS:0009 (InvalidHeader) must be returned because the elements are required. 

> MSH behaviour if TO/FROM is not recognised 
> -------------------------------------------
>
>                 Key: EBXMLMSG-47
>                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-47
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Improvement
>          Components: Core Spec
>            Reporter: Theo Kramer
>            Priority: Minor
>
> Section 5.2.2.2. eb:Messaging/eb:UserMessage/eb:PartyInfo states that TO/FROM are required yet there is no subsequent detail on the behaviour of the MSH if these are not recognised on a receiving MSH.
> Thanks to Michael Leditschke for raising this



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