Philipp Chudinov wrote: > John, there is no encoding attribute in my documents. they are all > UTF-8, and, since it is default encoding, I do not have this > attribute,but that is in_my_documents. You see, I have no idea where > it takes this encoding (see the sample below) > > <?xml version="1.0" encoding="ISO-8859-1"?> //I Do not know, where it > came from! My jsp page is UTF-8 too... io taglib is set attr utf-8
We may be going round in circles a little here.... If I understand this correctly you are generating the whole of the response (including the XML-RPC elements and the XML declaration) from a JSP page. So some part of the JSP process must be producing the XML declaration (forgive me if I have got this wrong - I am not a JSP/Struts developer). If you can modify your JSP system not to generate the XML declaration then replacing MinML with Xerces in the XML-RPC client should work. However, can you tell your JSP system to encode using ISO 8859/1? If you can tell it to encode in UTF-8 I would have thought that you could have told it to use some other encoding. This would let XML-RPC work "as is". > there is a method setEncoding() in apache xml-rpc. Could you provide > any code sample? Since Iam not so strong in abstract classes (this > method is at abstract XmlRpc.java) I just do not know yet how to > implement it in XmlRpc Handler... If it is possible to do somehow... Setting the system default encoding to UTF-8 (set the system property file.encoding to UTF-8) should make MinML (but not Xerces) treat the input bytes as UTF-8 encoded. Note this is a really nasty hack and may well break with a later XML-RPC release. John Wilson The Wilson Partnership http://www.wilson.co.uk
