[jira] Commented: (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:comment-tabpanel&focusedCommentId=12662824#action_12662824 ] 

Andreas Veithen commented on WSCOMMONS-418:
-------------------------------------------

Thilina,

The question is if we should (as you propose in your patch) simply generate IDs for attachments that don't have Content-IDs. An alternative would be:

1) Clean up the org.apache.axiom.attachments.Part, in particular remove deprecated methods and decouple it from JavaMail. Note that as far as I can see, this interface is currently not really part of the public API of Axiom but only used internally.

2) Enhance the Attachments class to allow client code to retrieve the attachments as a sequence of Part instances (with parts not required to have Content-IDs). Note that this implies that Part becomes part of the public Axiom API.

The additional benefit of this would be that it gives access to all the MIME headers of the attachments. This might e.g. be required to provide a full SAAJ implementation in Axis2.

> 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.