[ https://issues.apache.org/jira/browse/AXIS2-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Haeusler updated AXIS2-2505: ------------------------------------ Attachment: patch.diff I have identified the problem and have attached a patch for this bug. org.apache.axis2.saaj.SOAPPartImpl now honors the character encoding specified in the Content-Type header, or uses the InputStream constructor of STaX which will autodetect the correct encoding. I guess this is broken in all Axis 2 SAAJ releases. > 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 > Priority: Critical > 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]