On Fri July 24 2009 4:10:41 pm Benson Margulies wrote: > Look at the XML and see if it has a charset specified in the message.
Specifically in the Content-Type header. That is normally where it would be pulled from. Also, check your config for your webapp to see if you have any filters configured. I've seen a bunch of issues where poorly written filters will read in the stream to filter, then output it in a different charset or something and not update the Content-Type. Dan > > On Fri, Jul 24, 2009 at 2:03 PM, Kyle.Bober<[email protected]> wrote: > > I have consumed a WSDL from a .NET hosted service via Apache CXF 2.2.2. > > Sadly to my dismay when ever we receive a response from the service and > > it marshals the data into a string it doesn't convert the UTF-8 encoded > > characters properly. > > > > Such is an example. > > We make a request with an xml element containing the string value : > > turística > > We receive the raw response with the following string value: turÃstica > > and the following xml string value : turística > > > > But when the response data is marshaled in the code the java string's > > value is set to the follwoing : turÃstica > > > > Why is this happening and how can I enforce the UTF-8 CharacterSet??? > > > > Any help regarding this would be much appreciated! > > > > -Kyle > > -- > > View this message in context: > > http://www.nabble.com/UTF-8-Data-Marshalling-issue-tp24649219p24649219.ht > >ml Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] http://www.dankulp.com/blog
