[ https://issues.apache.org/activemq/browse/SM-784?page=comments#action_37793 ] Anders Hammar commented on SM-784: ----------------------------------
Ok, I'll need to look into this more in details next week but some quick comments: Yes, I think I want the encoding to be kept. If the data comes in as ISO-8859-1 (or some other encoding) it should stay that way. Now smx transforms it to UTF-8 and it also seems to be incorrectly transformed as Swedish characters are turned into garbage. (I need to investigate this more though. Earlier on I incorrectly though that UTF-8 couldn't handle Swedish characters and that was the problem, but I've been informed that it shouldn't be a problem and therefore it could just be some problem during the transformation). Having a property to specify the encoding is a solution, but I'd really like our smx-based solution to handle any incoming encoding and not only just one pre-defined (ISO-8859-1 for instance). Having said this, I was yesterday informed that UTF-8 can handle pretty much all characters and therefore it might not be a problem that messages are transformed (as long as the transformation is correct). However, error/fault messages should probably be in the same encoding as the incoming message as the sending app may not support UTF-8. Regarding the SourceTransformer class, having to set the output encoding seems weird and I'll try to investigate if this isn't an Xalan bug. I think that the encoding of the source should be used as default. I guess this is what you're talking about when you say it defaults to UTF-8. Do you know if this is this the correct behavior (according to doc/spec)? > No support for xml message encodings such as ISO-8859-1 > ------------------------------------------------------- > > Key: SM-784 > URL: https://issues.apache.org/activemq/browse/SM-784 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-core, servicemix-components, servicemix-soap > Affects Versions: 3.0.1 > Environment: Windows XP SP2 (Swedish), JDK 1.5.0_9 > Reporter: Anders Hammar > Attachments: HttpISO88591Test.java, JmsISO88591Test.java, > SoapMessageMarshalerTest.java > > > Servicemix only supports UTF-8 encoding, due to hard coded values. Support > for other encodings such as ISO-8859-1 is essential for countries such as the > Scandinavian ones. Xml has good support for this, and defined encoding in xml > messages should be honored. > The experienced problem occurs when passing an xml message (not soap, no > attachments) with encoding ISO-8859-1 defined, through servicemix. Problems > have been located in at least smx-core, smx-components, and smx-soap. > Attached are two test cases (one for http and one for jms) that shows this. > Use them with the http component and the jms component respectively (they use > test configuration existing within smx 3.0.1). > Another problem (duplicated characters) is related to a bug in woodstox. See > separate jira for that. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
