Github user oscerd closed the pull request at:
https://github.com/apache/camel/pull/2225
---
I'm forwarding this email from Chris Lambertus of Apache Infra. Please, for who
is able to do this, avoid to re-enable the Camel jobs until we find a solution.
Thanks.
--Andrea Cosentino --Apache Camel PMC
MemberApache Karaf CommitterApache Servicemix PMC MemberEma
GitHub user cpvandehey opened a pull request:
https://github.com/apache/camel/pull/2226
IAM role capabilities for s3 client:
https://user-images.githubusercontent.com/7979252/36284851-2f7363d6-125e-11e8-8722-c28f37dcc0b6.png";>
You can merge this pull request into a Git repository
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
GitHub user dmvolod opened a pull request:
https://github.com/apache/camel/pull/2225
CAMEL-12269: Bindy - Support regex expression as separator
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dmvolod/camel CAMEL-12269
Alternativ
Github user zregvart closed the pull request at:
https://github.com/apache/camel/pull/2224
---
