camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CAMEL-8346) JsonPathEngine skips file encoding
Date Thu, 26 Feb 2015 21:15:04 GMT


ASF GitHub Bot commented on CAMEL-8346:

GitHub user almondtools opened a pull request:


    The pull request contains also the patch to IOConverter, which is a separate pull request

You can merge this pull request into a Git repository by running:

    $ git pull CAMEL-8346

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #410
commit c213e65ee1bdb446f569dfdfe4950e7df85ce2bb
Author: Stefan Mandel <>
Date:   2015-02-14T17:31:37Z

    CAMEL-8356 IOConverter.toInputStream(file, charset) returns strange
    behaving stream

commit a9eb53b97df31face1d7fed860b94f8bee23065a
Author: Stefan Mandel <>
Date:   2015-02-26T20:04:36Z

    CAMEL-8346 JsonPathEngine skips file encoding


> JsonPathEngine skips file encoding
> ----------------------------------
>                 Key: CAMEL-8346
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jsonpath
>    Affects Versions: 2.14.1, 2.15.0
>            Reporter: Stefan Mandel
>             Fix For: 2.14.2, 2.15.0
>         Attachments:, germanbooks-iso-8859-1.json, germanbooks-utf8.json
> 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:
> # testing the same utf8-file under linux (default encoding:UTF-8) and german windows
(default encoding:windows-1252) leads to problems with german umlauts.
> # 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.

This message was sent by Atlassian JIRA

View raw message