[ http://issues.apache.org/jira/browse/XMLRPC-91?page=comments#action_12418023 ]
Jochen Wiedmann commented on XMLRPC-91: --------------------------------------- Another workaround might be to ensure that the server doesn't use Non-ASCII characters by using the ASCII encoding when sending the documents. Given the fact that MinML is practically obsolete with version 3, I'd like to close this issue with WONTFIX. I'll leave the request open for some weeks in case some other developer steps forward and volunteers to create a patch. > 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]
