[CAMEL-8346] JsonPathEngine skips file encoding

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.14.1, 2.15.0
• Fix Version/s: 2.14.2, 2.15.0
• Component/s: camel-jsonpath
• Estimated Complexity: Unknown
• Assignee: Willem Jiang
• Reporter: Stefan Mandel
• Created: 13/Feb/15 06:26
• Updated: 04/Mar/15 06:53
• Resolved: 04/Mar/15 06:53

Description

This occurs if one uses the camel file component with a charset parameter, e.g. file:/url?charset=UTF-8. It leads to strange effects:

1. testing the same utf8-file under linux (default encoding:UTF-8) and german windows (default encoding:windows-1252) leads to problems with german umlauts.
2. using a file in another encoding than the default (ISO-8859-1 on linux) leads also to problems with german umlauts.

• Both problems can be reproduced with the attached unit test files in 2.14.1.
• Problem 1 is hidden in 2.15-SNAPSHOT, because UTF-8 is hard-coded as file encoding (maybe ok, since JSON is almost never used with language specific encondings), Problem 2 also occurs in 2.15-SNAPSHOT

I can provide or help with a fix (or pull request), if these problems are classified as true defects.

Issue Links

• is blocked by: CAMEL-8356 IOConverter.toInputStream(file, charset) returns strange behaving stream