I replaced the hard coded "UTF-8" string in the SourceTransformer class with "ISO-8859-1" which seems to have fixed the issue. Now it works passing an ISO-8859-1 encoded message to the jms BC. However, the xml is somewhere transformed to UTF-8 encoding. Don't know where that happens...
This is a huge problem to us as we must support Swedish characters. Fixing any hard coded values to ISO-8859-1 would only be a quick fix as we should support other encodings as well. Should I file a jira for this? /Anders Anders Hammar wrote: > > > I think I've located the problem to the SourceTRansformer class, in which > UTF-8 is hard-coded. At least this causes some of the problems (when trace > logging the message). WHat happens is that the incoming message is > transformed to a byte array and then read as if it was UTF-8 encoded > (which it isn't). > -- View this message in context: http://www.nabble.com/Problem-with-ISO-8859-1-encoding-and-jms-component-tf2767158s12049.html#a7719473 Sent from the ServiceMix - User mailing list archive at Nabble.com.
