[ https://issues.apache.org/activemq/browse/SM-784?page=comments#action_37792 ] Guillaume Nodet commented on SM-784: ------------------------------------
Author: gnodet Date: Fri Dec 29 10:45:10 2006 New Revision: 491075 URL: http://svn.apache.org/viewvc?view=rev&rev=491075 Log: SM-784: No support for xml message encodings such as ISO-8859-1 Modified: incubator/servicemix/trunk/core/servicemix-core/src/main/java/org/apache/servicemix/jbi/jaxp/SourceTransformer.java I've just looked at the test cases you attached (sorry for the delay ...). But I'm not not sure what the real problem is. I don't see any illegal transformation and the only problem i see is that you want the data to be kept in iso-8859-1, whereas it is currently transformed in UTF-8. However, the data itself it still correct, right ? Each time an xml transformation is performed (converting from string to DOM, DOM to string), the output encoding is currently not specified, which means it defaults to UTF-8 afaik. I will first change that so that it can be overriden by a system property or by changing the SourceTransformer.defaultCharset It seems that the HTTP test case can now works if you set this property to ISO-8859-1 at the beginning of the test. I guess the http response could use the same encoding than the request though ... > 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
