[
https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913756#action_12913756
]
Andreas Veithen commented on AXIS2-4828:
----------------------------------------
Rich,
In Axiom 1.2.9 I introduced a new API (meant as a replacement for
MIMEOutputUtils; see WSCOMMONS-553) that entirely gets rid of the StringWriter
stuff:
http://ws.apache.org/commons/axiom/apidocs/org/apache/axiom/mime/package-summary.html
The API itself even allows streaming of the parts (although the JavaMail based
default implementation is not able to leverage this; see WSCOMMONS-554). Axiom
uses this API internally to produce XOP/MTOM, but porting SOAPMessageFormatter
to that new API is part of the unfinished work. Maybe this JIRA is an
opportunity to rewrite that part of SOAPMessageFormatter properly once and for
all?
> SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when
> doing SWA
> ----------------------------------------------------------------------------------
>
> Key: AXIS2-4828
> URL: https://issues.apache.org/jira/browse/AXIS2-4828
> Project: Axis2
> Issue Type: Bug
> Components: kernel
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Background:
> The SOAPMessageFormatter writes the message to an OutputStream in all cases
> except SWA.
> Writing to an OutputStream is faster and allows the other components to
> access the OutputStream.
> Proposal:
> I am making a small change to the SOAPMessageFormatter SWA flow to use a
> ByteArrayOutputStream as the buffer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
