ansaurus

Question

JAX-WS errors when SOAP body contains UTF-8 BOM

Answer 1

+1 A:

One workaround idea: add filter on the web application that just consumes the BOM before passing on the request document to the JAX-WS service.

ankon 2009-10-28 20:20:06

I toyed with the idea of doing just that but that seems like such a hack. JAX-WS should be able to handle this and I'd hate to a filter and another layer to trim characters off the request. If I don't get an answer, I may go down that route. Thanks Ankon.

Vinny Carpenter 2009-10-28 20:52:09

Answer 2

A:

We had a similar problem writing a .Net client to a 3rd party Java webservice, .Net included the Byte order mark and the Java service would throw an exception.

The 3rd party SOAP method took a single string as an argument, and that string was an XML document (I love people who don't really understand what problem SOAP is trying to solve!) By default .net added the UTF-8 byte order mark to the "payload" xml document, which is strictly correct, but in practice causes problems.

In our case we found two possible solutions from the client (.net) end. I'm not sure how easy this will be to do from SQL Reporting services though.

String.Trim() - The xml had to get put into a string before passing into the soap method, calling .Trim() removed the byte order mark. Easy.

The second method was to set the UTF encoding settings on the XmlWriterSettings slightly differently, something like the following:

XmlWriter xmlWriter = null;
XmlWriterSettings settings = new XmlWriterSettings();
settings.Indent = true;
settings.Encoding = new UTF8Encoding(false);
xmlWriter = XmlWriter.Create(xmlSteam, settings);

The important bit is the "new UTF8Encoding(false);", that argument is "encoderShouldEmitUTF8Identifier" and pretty much solves the problem.

Andrew M 2010-09-14 12:23:48

ansaurus

tags:

views:

answers:

JAX-WS errors when SOAP body contains UTF-8 BOM

related questions