I have the following route running in ServiceMix (v4.4.2) using Camel v2.8.5:
from(jms:queue:msci.start)
.routeId(start-route)
.transacted()
.process(new Processor() {
@Override
public void process(Exchange exchange) throws
Thanks Claus, just the trick.
--
View this message in context:
http://camel.465427.n5.nabble.com/Splitting-within-transactions-tp5719539p5719573.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi all,
I have a route that looks something like this, running in ServiceMix
(v4.4.2):
from(jms:queue:start)
// Message processing
.(jms:queue:end);
I would like to protect against the server crashing whilst processing this
route so that if the message is not lost in transit. What is
For anyone who finds this in future, this did the trick for me:
from(REQUEST_QUEUE_ENDPOINT)
.split(body(), new AggregationStrategy() {
public Exchange aggregate(Exchange oldExchange,
Exchange newExchange) {
Hi all,
I would like to take a message containing a list of objects, split the list
into it's component objects, process them in parallel, aggregate the
modified objects back into a list.
I am using camel 2.8.0.
From what I can see I need to use a route in the following form:
Claus to the rescue! Thank you very much, works like a charm. Nice book by
the way.
Ben
--
View this message in context:
http://camel.465427.n5.nabble.com/Splitting-processing-and-aggregating-a-list-tp5716013p5716015.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi all,
I am (attempting) to use SOAP over JMS within Fuse ESB (v4.4.1-fuse-06-03).
I have a web service in one bundle that I wish to call from another. The
service exposes a simple getAll() method which return a list of Users. I
have had the wsdl/Java code running as a conventional web service
Hi all,
I am (attempting) to use SOAP over JMS within Fuse ESB (v4.4.1-fuse-06-03).
I have a web service in one bundle that I wish to call from another. The
service exposes a simple getAll() method which return a list of Users. I
have had the wsdl/Java code running as a conventional web service