You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2018/10/01 11:19:00 UTC

[jira] [Created] (CAMEL-12844) splitter with grouping looses encoding property

Claus Ibsen created CAMEL-12844:
-----------------------------------

             Summary: splitter with grouping looses encoding property
                 Key: CAMEL-12844
                 URL: https://issues.apache.org/jira/browse/CAMEL-12844
             Project: Camel
          Issue Type: Bug
          Components: camel-core
    Affects Versions: 2.22.0, 2.21.0
            Reporter: Claus Ibsen
             Fix For: 2.21.3, 2.22.2, 2.23.0


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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)