[
https://issues.apache.org/jira/browse/AXIOM-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071656#comment-13071656
]
Andreas Veithen commented on AXIOM-377:
---------------------------------------
The proposed change would only work in a very limited set of scenarios. In
particular for XOP/MTOM it is only guaranteed to work in scenarios where the
message has a single element of type base64binary. In cases where there are
multiple optimized elements, Axiom would not be able to make sure that the
message can be serialized successfully. That is because of the following
requirement in the XOP specs:
"Except for purposes of determining the root MIME part, as specified by [RFC
2387], ordering of MIME parts MUST NOT be considered significant to XOP
processing or to the construction of the XOP Infoset."
We need to think more carefully about this to come up with a solution that
covers all reasonable scenarios.
> When a multipart message is built, there should be a way to retrieve a
> DataHandler to the MTOM part without reading the entire incoming stream
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIOM-377
> URL: https://issues.apache.org/jira/browse/AXIOM-377
> Project: Axiom
> Issue Type: New Feature
> Reporter: Sadeep Jayasumana
> Attachments: AXIOM-377.patch
>
>
> This feature is particularly useful when large attachments are used. Building
> large attachments in memory drives the system OOM and building them on files
> dramatically reduces performance.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
