[CAMEL-12844] splitter with grouping looses encoding property

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.21.0, 2.22.0
• Fix Version/s: 2.21.3, 2.22.2, 2.23.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 01/Oct/18 11:18
• Updated: 01/Oct/18 11:19
• Resolved: 01/Oct/18 11:19

Description

Reported on user list and today also on gitter
http://camel.465427.n5.nabble.com/File-Encoding-falls-back-to-default-encoding-while-grouping-after-split-using-tokenize-td5797769.html

Jakob Krejberg Ørhøj @jakoborhoj_twitter Sep 28 12:30
Hello. I've been battling with some encoding issues when using split().tokenize() in Camel. I am having the same issue as described in: http://camel.465427.n5.nabble.com/File-Encoding-falls-back-to-default-encoding-while-grouping-after-split-using-tokenize-td5797769.html. Is it a bug that Camel does not pass the exchange to the converter so that it can get the encoding set in the exchange? Currently it will always default to UTF-8 as I see it.