[jira] Updated: (WSCOMMONS-418) Axiom MIME parser does not support MIME parts without content-id's

["Andreas Veithen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WSCOMMONS-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Veithen updated WSCOMMONS-418:
--------------------------------------

    Fix Version/s: Axiom 1.2.9
       Issue Type: Bug  (was: Improvement)

This is actually not only relevant for the mail transport, because the SwA specification doesn't require the presence of a Content-Id header in each attachment. Indeed, the spec says:

[quote] A "SOAP message package" contains a primary SOAP 1.1 message. It may also contain additional entities that are not lexically within the SOAP message but are related in some manner. [...] The primary SOAP 1.1 message in a message package may reference the additional entities. [...]

Referenced MIME parts must contain either a Content-ID MIME header structured in accordance with RFC 2045, or a Content-Location MIME header structured in accordance with RFC 2557.[/quote]

Thus the specification clearly allows attachments that are not referenced by the SOAP message, and these attachments are not required to have Content-Id headers. The behavior you describe therefore violates the SwA spec and should be considered as a bug.

> Axiom MIME parser does not support MIME parts without content-id's
> ------------------------------------------------------------------
>
>                 Key: WSCOMMONS-418
>                 URL: https://issues.apache.org/jira/browse/WSCOMMONS-418
>             Project: WS-Commons
>          Issue Type: Bug
>          Components: AXIOM
>            Reporter: Thilina Gunarathne
>            Assignee: Thilina Gunarathne
>             Fix For: Axiom 1.2.9
>
>         Attachments: axiom_mixed_content_patch.txt
>
>
> Axiom MIME parser does the content-id validation for the MIME parts as required by MTOM & SwA..Also the Attachments API is designed as a map (content-id, attachment) with this assumption.. 
> But now the mail transport is going to use the same MIME parser and they have valid messages which does not have content-id's for MIME parts. But IMHO trying to generalize all axiom/Axis2 attachment API's would be a too much of an API change at this point of the project... 
> Attached is a quick patch to generate a UUID in place of the missing content-id... But with this we are going to miss the content-id validation...
> WDYT?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.