Kurt, Good, I think the encoding-specification through setEncoding should still work, though I did not test if and, of course, at the possible risk that your string contains non-encodable characters.
If the encoding has been specificied with XmlRpc.setEncoding then it should work. Well... it should. The problem is that the method XmlRpc.setEncoding does nothing for the encodings table which associates XML encoding names to java encoding names. This method should really be "setEncoding(java-encoding, iana-encoding)" (where iana-encoding is the encoding that should appear in the name of the XML header, it is specified by IANA (don't find the reference anymore). So you may be lucky: if your encoding name is the same in java and iana then you're out. Otherwise, please submit encoding-table enrichments ! Paul On Mercredi, mars 6, 2002, at 03:24 , Kurt Ward wrote: > Paul, > > This is great! We have the need to send UTF-8 encoded strings > to an application and feel that SOAP is a little overkill for > what we are trying to do. Hopefully this can get worked into > CVS. > > One suggestion though: I would like to have the option of specifying > the encoding. > > Thanks! > Kurt
