[
https://issues.apache.org/jira/browse/AXIS2-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sumedha rubasinghe resolved AXIS2-2505.
---------------------------------------
Resolution: Fixed
Fix Version/s: nightly
The revision used to create the patch is quite old & the SOAPPartImpl has
changed quite a lot. So I modified the code to include the changes done in the
patch. Thanks for the patch.
I am have also added a test case
org.apache.axis2.saaj.integration.IntegrationTest ->
testSendReceive_ISO88591_EncodedSOAPMessage() to test this.
Thank you.
> SOAP XML character encoding is not handled at all, when constucting message
> from InputStream
> --------------------------------------------------------------------------------------------
>
> Key: AXIS2-2505
> URL: https://issues.apache.org/jira/browse/AXIS2-2505
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.1.1, 1.1, 1.0
> Reporter: Michael Haeusler
> Assignee: sumedha rubasinghe
> Priority: Critical
> Fix For: nightly
>
> Attachments: patch.diff
>
>
> whenever an existing SOAPMessage is read from an InputStream, the XML parser
> will use the system default encoding to decode the characters.
> obviously this will not work if it doesn't match.
> MimeHeaders headers = new MimeHeaders();
> headers.addHeader("Content-Type", "text/xml; charset=iso-8859-1");
> FileInputStream dataStream = new
> FileInputStream("test-resources/interop/soap-env-iso.xml");
>
> SOAPMessage message = MessageFactory.newInstance().createMessage(headers,
> dataStream);
> now if there is any special character in the xml file it will result in bad
> data.
--
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]