Hi
Yeah from the git history and the source code it seems like we should
restore the old one after the conversion.
You are welcome to log a JIRA and provide a PR
On Thu, Feb 15, 2018 at 7:38 PM, Quinn Stevenson
wrote:
> I found a situation where Camel isn’t doing what I expected, and I wanted to
Hmmm….
I would expect that if the character set was already on the exchange before the
call, it should still be there after the call - that is the issue I hit - it
was removing the CamelCharsetName exchange property that was already there. If
the charset is specified on the convertBodyTo, I th
I would not say that it's a bug.
Actually, when convertBodyTo ends up decoding bytes to string, I would
expect the charset to be removed.
When convertBodyTo ends up encoding a string into bytes, I would expect the
charset to be overridden (I don't think that it is the current
implementation however
I found a situation where Camel isn’t doing what I expected, and I wanted to
ask the developers before I created the JIRA and changed the behavior that I
believe is a bug.
What I’m seeing is when I call convertBodyTo with a both type and a character
set supplied and the exchange already has a c
