Next in thread → Next in month →

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

From
OASIS Issues Tracker <>
Date
2014-12-03T20:47:15+00:00
ID
Thread
[OASIS Issue Tracker] (EBXMLMSG-47) MSH behaviour if TO/FROM is not recognised
[ https://issues.oasis-open.org/browse/EBXMLMSG-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52641#comment-52641 ] 

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

Passing ebMS meta-data to the business application is not a requirement of the ebMS specification so the alternative proposal is not feasible. 

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