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: [OASIS Issue Tracker] Commented: (EBXMLMSG-46) Non-referenced MIME parts

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

Pim van der Eijk commented on EBXMLMSG-46:

We could define the (abstract) "Deliver" operation to only deliver payloads with a UserMessage that are referenced from that UserMessage.  This would support the Part 2,  Bundling feature that allows multiple UserMessage structures.  When delivering a specific UserMessage, all payloads not referenced from that UserMessage's PayloadInfo are silently ignored.

We could have a generalized constraint on ebMS messages that each payload has to be referenced by some PayloadInfo in some UserMessage.  

However,  there could be more exotic intermediary protocols (other than our transparent ebMS3 intermediaries) or higher-level SOAP protocols where an unreferenced payload makes sense. 

In any case the constraint could be added in AS4. 

> Non-referenced MIME parts
> -------------------------
>                 Key: EBXMLMSG-46
>                 URL: http://tools.oasis-open.org/issues/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 is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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