[
https://issues.apache.org/jira/browse/AXIOM-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073158#comment-13073158
]
Andreas Veithen commented on AXIOM-326:
---------------------------------------
I think that it is possible to replace our custom MIME parsing code with mime4j
without breaking any existing public APIs, with one (potential) exception,
namely Attachments#getIncomingAttachmentsAsSingleStream(). Probably once we
hand over the input stream to mime4j it will probably (to be confirmed) no
longer be possible to give access to that stream in a well defined state. The
reason is that we have no control over how much buffering mime4j does.
However:
* I didn't find a single piece of code that is using
getIncomingAttachmentsAsSingleStream().
* The method was introduced by AXIOM-329, but that use case should be covered
by a proper solution for AXIOM-377 (which in turn depends on the present issue).
Therefore it is reasonable to sacrifice getIncomingAttachmentsAsSingleStream
(if necessary).
> MIME message parser and serializer based on Apache mime4j
> ---------------------------------------------------------
>
> Key: AXIOM-326
> URL: https://issues.apache.org/jira/browse/AXIOM-326
> Project: Axiom
> Issue Type: Improvement
> Reporter: Oleg Kalnichevski
>
> MIME message parser and serializer based on Apache mime4j
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org
For additional commands, e-mail: dev-h...@ws.apache.org
