Hi, It can be characterset issue. Try to figure out, what data is being saved in both application? are you sure that in app A and app B you are trying to save same non-ascii characters? if you are reading the inputstream before creating the SOAP, please use a characterset to read the inputstream (i.e. new BufferedReader(new InputStreamReader(request.getInputStream(), "UTF-8"));).
Chinmoy On Thu, May 28, 2009 at 3:24 AM, pfconrey <pfcon...@hotmail.com> wrote: > > I’ve come across an issue I can’t seem to figure out. I have two > Java/Spring/Tomcat web applications that consume the same web service. When > I save non-ASCII characters in application "A", everything works correctly. > However, when I do the same, using the same characters, in application "B", > the client encodes the data differently when it builds the SOAP envelope: > > Application "A": ßtressë (this is correct) > Application "B": ßtressë (This causes > double-encoding) > > It appears that "B" is encoding the data to UTF-8, then xml-encoding the > resulting bytes, whereas "A" is xml-encoding the Unicode code points. I > can’t find anything in the code or configuration that would cause this, and > all underlying libraries have been synced between the two applications. > > Any insight you can offer would be appreciated. > > If it would help to post some code snippets, I'd be glad to do so. I'm just > not sure what section would be most relevant since it appears the problem > manifests itself inside of the Axis libraries. > Edit/Delete Message > -- > View this message in context: > http://www.nabble.com/Problem-with-SOAP-Serialization-of-non-ASCII-characters-tp23751476p23751476.html > Sent from the Axis - User mailing list archive at Nabble.com. > >
