Hi, I am also having some problems with unicode characters, more specifically extended unicode characters, not being processed as I expected it to by the file component. The only way I can get it working is by explicitly converting to string before routing to the file component. Tests with a simple Euro sign work either way. To me it seems that this should not be necessary and should normally make no difference.
I will try to add (upload) a testcase that demonstrates the issue: ExtendedUnicodeTestJiraDmBack414.java <http://camel.465427.n5.nabble.com/file/n5730396/ExtendedUnicodeTestJiraDmBack414.java> Note that when using just Camel + Jdk, both tests with extended unicode characters will fail, because of a Xalan bug (see https://issues.apache.org/jira/browse/XALANJ-2560). By including saxon on the classpath, the test "testSendExtendedUnicodeMessageExplicitToString" will succeed. But the test "testSendExtendedUnicodeMessage" will still fail. I hope everything is clear, if not let me know. Luc. -- View this message in context: http://camel.465427.n5.nabble.com/UTF-8-and-Files-Created-by-Camel-tp5053652p5730396.html Sent from the Camel - Users mailing list archive at Nabble.com.
