Hi all
This is my SO question about Rest paths:
http://stackoverflow.com/questions/27707664/whats-wrong-in-my-apache-camel-rest-paths
Many thanks for any hint
Happy 2014 ending! :)
Hi Neeraj
The value of the property attributeNames really refers to an object in the
registry just like amazonSQSClient.
So you need to have something like:
registry.put(All, Collections.singletonList(All));
It may be less confusing if you renamed the value to something like
attributeList:
Hi Christoph!
I raised the JIRA https://issues.apache.org/jira/browse/CAMEL-8201 and start
working on it.
I could successfully check, the issue is in Camel and not in JRuby. Add
yourself as watcher on the JIRA to keep you up to date...
Best,
Christian
--
View this message in context:
I just fired up a sample app based on the file-size CBR I mentioned, hope I
didn't misunderstand or oversimplify so take a look if you haven't solved
it yet.
https://github.com/levackt/samples/tree/master/file-size-cbr
Also take a look at the route throttling example which shows off the
policies
Dear Camel Users,
We have a couple of camel contexts and have a scenario where we need to
invoke a synchronous call to a route in different camel context. We have
used direct endpoint for synchronous call within same camel context ,we
would like to have same behavior for different camel contexts.
I would suggest that you take a look at the direct-vm component.
http://camel.apache.org/direct-vm.html
Best regards
Pontus
On 31 Dec 2014 14:49, leofprince leofpri...@gmail.com wrote:
Dear Camel Users,
We have a couple of camel contexts and have a scenario where we need to
invoke a
Hi,
On a similar design, we leverage to workaround the same constrains using
servlet/restlet bind point on remote instance.
Advantage : it covers header transmission questions, synchronously, in
transnational mode, without use activemq or jms.
Disadvantage : it can create issues with
