[ http://issues.apache.org/jira/browse/XMLRPC-91?page=comments#action_12418426 ]
Jochen Schwarze commented on XMLRPC-91: --------------------------------------- You cannot normally influence the XML encoding that a client uses to conact your server, so that's no workaround IMO. But here's another workaround, this time without Xerces in the classpath: XmlRpc.setDriver(org.xml.sax.helpers.XMLReaderAdapter.class); No need for a patch to MinML on my side. Jochen > MinML does not handle XML encoding properly > ------------------------------------------- > > Key: XMLRPC-91 > URL: http://issues.apache.org/jira/browse/XMLRPC-91 > Project: XML-RPC > Type: Bug > Versions: 2.0 > Reporter: Jochen Schwarze > > When you implement your own XML-RPC transport layer and call > XmlRpcServer.execute(InputStream in, XmlRpcContext context); > the following happens: > First, XmlRpc.parse(InputStream is) calls MinML.parse(new InputSource(is). > Then, MinML.parse(...) calls parse(new > InputStreamReader(source.getByteStream())); > which is wrong: this parses the stream with the platform default encoding, > regardless of the actual encoding used in the XML stream, destroying, eg, > UTF-8 encoded characters on Windows. > Together with #XMLRPC-90, XmlRpc could be changed to use the Java 1.4 oder > 1.5 platform XML parser which respect handle streams correctly and use any > encoding declaration embedded in the XML stream. > Workaround: Use XmlRpc.setDriver("xerces") and add xercesImpl.jar to the > classpath. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
