I see this post is from about a year ago and have not been able to find any
other information regarding updates on this kind of use case. Does anyone
know if there are any new capabilities or plans to add them that would allow
a webservice to pull data via the jpa component?
It would be really
Thank you Claus. The SQL component works great for my use case, although I
can see where there would a few minor drawbacks to using it versus updating
the JPA component to work in a similar fashion (Perhaps something I could
contribute to if I get the time).
1. In my use case, my database fields a
I really like the camel REST DSL, but would like to make my servlet container
to not hold onto http request handling threads when processing REST
requests. Is there a way to specify this via the REST DSL? What I am
looking for is something that works similar to spring's DeferredResult. I
would
I have found lots of documentation on how to manipulate an array in simple
but none on how to create one. Is this possible? I have a bean with method
whose first parameter is an object second parameter is an array of strings.
My method signature is like so:
myMethod(MyObjectType o, String ...
Thanks for getting back to me about this. Too bad that array creation is not
supported. What I was trying to do with my bean method was to provide
validation to check whether or not one of the properties of my object was
equal to one of the values in the array. I just found an alternate solutio
Thanks again. That made the code a bit cleaner. It took a minute to figure
out the exact syntax but that makes the code now:
${body.mypropertytovalidate} in
'STRING1,STRING2,STRING3'
--
View this message in context:
http://camel.465427.n5.nabble.com/Define-an-array-in-simple-tp5770637p5770701
I have an application that runs on several servers but I want certain routes
to run on only one server in the group. To achieve this I implemented a
Zookeeper route policy. It seems to work for most of my routes. When they
attempt to start up on any node except the one with the zookeeper lock, t
After further findings, it turns out that the route policy is respected. The
reason I thought it wasn't is because the route is not stopped on the
non-master servers until the first time the ftp consumer actually finds a
qualifying file to download. I was seeing logging from my filter code
running