On March 13, 2014, Phil Mocek wrote:
Must percent-encoded special characters in a Camel message endpoint URI
be wrapped in RAW() in order for Camel to correctly process the URI?
Nobody answered my question. Off-list last week, I e-mailed Camel
contributor Claus Ibsen, who is named in relevant
On Tue, Mar 18, 2014 at 5:03 PM, Phil Mocek phil-li...@mocek.org wrote:
On March 13, 2014, Phil Mocek wrote:
Must percent-encoded special characters in a Camel message endpoint URI
be wrapped in RAW() in order for Camel to correctly process the URI?
Nobody answered my question. Off-list last
Hi Phil,
You can find the special characters which we handled in camel here[1], maybe we
need to revisit the unsafe characters again in new version of Camel.
[1]
https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/camel/util/UnsafeUriCharactersEncoder.java
--
Must percent-encoded special characters in a Camel message endpoint URI
be wrapped in RAW() in order for Camel to correctly process the URI?
For example: I believe the following is a valid [Camel endpoint URI of
schema aws-sqs][1]:
RAW() should work in your case.
You can also use the amazonSQSClient option to let camel lookup the configured
client for you as a workaround.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter:
Willem Jiang wrote:
RAW() should work in your case.
Thanks, but that's not what I'm asking. I can find out of it works by
trying. I want to what is expected to work---how Camel is supposed to
work. I don't want to write software based on buggy behavior unless I'm
aware of the bug and what I'm
