[
https://issues.apache.org/jira/browse/WSCOMMONS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886425#action_12886425
]
Myles Bunbury commented on WSCOMMONS-550:
-----------------------------------------
A quick scan of the OMTextImpl.java file in trunk indicates that this issue is
likely still in the code, even though there has been some changes involving
base 64 encoding in this area.
> OMTextImpl.getText() only works once with a datahandler
> -------------------------------------------------------
>
> Key: WSCOMMONS-550
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-550
> Project: WS-Commons
> Issue Type: Bug
> Components: AXIOM
> Affects Versions: Axiom 1.2.8
> Reporter: Myles Bunbury
>
> When OMTextImpl relies on an underlying datahandler's inputstream, a call to
> getText() can be a one shot deal. Once the datahandler's inputstream is
> consumed, the encapsulated data is lost and subsequent calls to getText()
> return "".
> I ran into this situation using Synapse with debug logging enabled. A debug
> log message printed out the entire SOAP envelope to the log, thereby
> consuming the binary data wrapped by OMTextImpl. When later on the SOAP
> envelope was transmitted via the SendMediator, the OMTextImpl could no longer
> supply the data.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
