I am having a similar problem that the failed message was not moved to the
dead letter queue (regardless whether the dead letter queue is a jms
endpoint or file endpoint). I experienced this problem in both Camel 2.11.1
and 2.12.1. The redelivery part works, just the failed message was not
moved.
To start I just want to let you know I am new to Camel and very recently I
grasped its main concepts.
I am trying to create a basic working example using Apache-Camel with
ActiveMQ as a broker and using jms-component as a client of a loadbalancer
using the failover construct. All this is done usin
http://www.pretechsol.com/2013/11/camel-selective-consumer-using-jms.html#.UnUWLxAVuPA
--
View this message in context:
http://camel.465427.n5.nabble.com/Message-selector-example-tp5713805p5742545.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Anyone got any suggestions at all?!!?
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-stop-URLDecoding-on-path-of-URI-NOT-query-parameters-tp5742409p5742546.html
Sent from the Camel - Users mailing list archive at Nabble.com.
You can use an aggregation strategy on the splitter to merge any
changes you want on the exchange that is routed after all the
splitting is done.
By default the exchange being routed is a copy of the input exchange
(untouched).
On Fri, Nov 1, 2013 at 7:36 PM, javamonkey79 wrote:
> With following
Hello folks,
On the Code Ranch (formerly the Java Ranch), a question was posted relative to
the Apache Camel Components Poster promotion, of which I cannot answer:
Here is the question:
Camel seems to offer a better developer
experience (via the Fluent API) than Spring Integration; and cert
Hi
first of all, I would say that your formula Camel + ActiveMQ is almost right.
What you might be missing is your runtime, where you deploy Camel to. This
might be the point why people have guided you towards Fuse, JBoss, Talend, etc.
Fuse, Talend, etc. provide additional tooling to implement
Ok... so I am still struggling with understanding some of Camel's main
features and limitations.
My objective is to implement a demo application that can migrate camel
endpoints. To achieve this everyone suggested that I should use the camel
load-balancer pattern with the failover construct (so fa
Thanks, Claus. Looks like the javax.xml.xpath.XPathFactory.setFeature()
functionality could potentially be leveraged at some point to do this.
If camel exposed access to this standard method and a route was configured
to use the saxon parser then it looks like we could leverage the saxon
featur
Hi,
Thanks for responding. The transactions are not committed even when there
are no exceptions.. transacted() does not seem to do any job..
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-transacted-route-tp5742362p5742528.html
Sent from the Camel - Users mailing lis
10 matches
Mail list logo