On 12/15/06, Anders Hammar <[EMAIL PROTECTED]> wrote:
Ok, I've traced the problems for my test case and found out that there are several problems that makes smx to work with only UTF-8 xml. I've also found out that there are problems with libraries that smx uses (woodstox for instance). The problems I've found within smx are these (all related to smx 3.0.1): org.apache.servicemix.jbi.jasp.SourceTransformer (servicemix-core): 1. UTF-8 is hard coded as the default (and only) encoding, which is used in the toDOMSourceFromStream(StreamSource) method. Not sure the reason for this, because it works for me (in the ISO-8859-1 case) when just removing the setting of this encoding on the InputStream. 2. In the toResult(Source, Result) I need to set the output encoding on the transformer. Possibly this is an Xalan bug, as the encoding is correct in the Source. However, setting the encoding as an output property on the transformer before the transformation fixes this. org.apache.servicemix.soap.marshalers.SoapWriter (sevicemix-soap): 1. In method writeSimpleMessage(OutputStream), when creating the XmlStreamWriter the encoding needs to be passed along. Otherwise the output will be in the wrong encoding. Also, a bug in woodstox 3.0.2 duplicates some characters. This is a known bug, which has been fixed in the woodstox trunk. I've filed a jira to included an updated version when that comes out. I'll file jiras for the servicemix specific problems. I also need to check that this actual does make it work for my real scenario and not just the test case. :-)
Yes, please raise JIRA and attach all the test cases / patches you have :) And thanks a lot for your hard work ! -- Cheers, Guillaume Nodet
