[
https://issues.apache.org/jira/browse/WSCOMMONS-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662837#action_12662837
]
Thilina Gunarathne commented on WSCOMMONS-418:
----------------------------------------------
Regarding your first comment,
* Axis2 does support unreferenced MIME parts
* We have documented the behavior that Axis2 does not support Content-Location
based MIME part addressing.
I agree that the API's we have at the moment for attachment handling are
suboptimal, specially given that Axiom/axis2 MIME handling API's were designed
initially to support only MTOM. Then later we added SwA , SAAJ and mail
transport on top it making things far more complicated.. I'm sure a careful
design, while having all the requirements on table, will lead us to a cleaner
solution. We should also try to integrate mime4j as an option too..
My only concerns are,
1. I no longer have free cycles for a big change and to maintain it till it
gets stabilized :)... But I'm always willing to give a hand if somebody is
going to take this up.
2. Backward compatibility & code stability issues.
> 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.
