Re: routeContext and startOrder attribute

2014-02-26 Thread erstanl
Claus, my apologies. That works just fine. I had an XML errors in another location. Thanks! -- View this message in context: http://camel.465427.n5.nabble.com/routeContext-and-startOrder-attribute-tp5747788p5748024.html Sent from the Camel - Users mailing list archive at Nabble.com.

routeContext and startOrder attribute

2014-02-21 Thread erstanl
Hello, I am in a bind. I like the idea of a routeContext, as a way to extract common routes for usage by others. The problem I am running into, is that you cannot add a startOrder attribute to a route defined in a routeContext. Is there another way to control how routes that imported via routeCon

Re: transactions that span multiple routes

2013-06-22 Thread erstanl
Thanks for the response Christian, and sorry for my delay. Christian Mueller wrote > I do not have a solution at present, but I'm wondering what happens if you > commit the exchange (than the message is deleted from the queue and the > database is updated) and than your route fails? > Also as far

http4 to blast requests

2013-02-04 Thread erstanl
Can someone explain to me what this route is doing? from("direct:registerStuff") .threads(19) .to(String.format( "https4://%s?authUsername=%s&authPassword=%s",

Re: Spring XML configuration variables

2013-01-18 Thread erstanl
Thanks for the quick reply Claus. For those who run into the same issue, this was the change I made to the route: And more importantly, I had to comment out my spring and implement this: So I replaced this: with this: All is well at the Camel fa

Spring XML configuration variables

2013-01-18 Thread erstanl
Sorry if this is the wrong forum for this question. I am trying to build a camel route that consumes from a JMS queue and uses a selector. The problem is, I would like to use a selector based upon a spring variable. I can't seem to convince spring/camel to dereference that variable. What am I missi

Re: transactions that span multiple routes

2013-01-09 Thread erstanl
Willem, thanks for the idea. Here is a resulting issue I have run into. The 1st route takes a message from queue/batch/ready, it throws it into the seda queue. It basically takes every message it can and stuffs it into the seda queue as fast as it can. The second route does process them as I would

transactions that span multiple routes

2012-12-06 Thread erstanl
Here is the use case. 1) Consume message from ActiveMQ queue 2) Update database with data derived from step 1 3) Download rather large data from database 4) Process data from step 3 5) Update database with results from step 4 These routes represent that case (I think): Steps 1, 2

Splitting a stream from a servlet

2012-05-29 Thread erstanl
All, I have a camel servlet that is consuming an XML stream. I currently have it splitting that stream successfully. The problem is that I need to split it multiple times. There are 2 sections in the stream that I am interested in. Once I have those split out, I intend to forward them as JMS messag