You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2016/04/28 22:45:12 UTC
[jira] [Updated] (AXIOM-31) Axiom MIME parser does not support MIME
parts without content-id's
[ https://issues.apache.org/jira/browse/AXIOM-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated AXIOM-31:
---------------------------------
Affects Version/s: 1.2.18
Fix Version/s: 1.3.0
> Axiom MIME parser does not support MIME parts without content-id's
> ------------------------------------------------------------------
>
> Key: AXIOM-31
> URL: https://issues.apache.org/jira/browse/AXIOM-31
> Project: Axiom
> Issue Type: Bug
> Components: API
> Affects Versions: 1.2.18
> Reporter: Thilina Gunarathne
> Assignee: Andreas Veithen
> Fix For: 1.3.0
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org