[OASIS Issue Tracker] (EBXMLMSG-46) Non-referenced MIME parts

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

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

Sander Fieten commented on EBXMLMSG-46:
---------------------------------------

Although I think there should be no other MIME parts then for SOAP envelop and payloads adding an additional constraint may be too restrictive. It is also more than an erratum.

I therefore prefer to have the solution Pim describes above to ignore the not referenced MIME parts on delivery to the Consumer application. And maybe generate an Error with severity warning.

> Non-referenced MIME parts
> -------------------------
>
>                 Key: EBXMLMSG-46
>                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-46
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Improvement
>          Components: Core Spec
>            Reporter: Theo Kramer
>            Priority: Minor
>
> Section 5.1.5 Payload Containers states the following
> The contents of each Payload Container (including the SOAP Body) MUST be identified in
> the /eb:Messaging/eb:UserMessage/eb:PayloadInfo element.
> Yet the previous paragraph reads as follows
>  An MSH MUST NOT process application data that is not referenced by eb:PayloadInfo.
> Does this imply that a message must be rejected if a message is received with a payload container that is not referenced by eb:PayloadInfo ?
> An alternate approach would be to never send a message with attachments that are not referenced by the eb:PayloadInfo, and ignore (drop) any attachments that are not referenced in eb:PayloadInfo for received messages with an appropriate message in the logs. So could be interpreted as 'The contents of each *valid* Payload Container ...'
> Thanks to Michael Leditschke for raising this



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