Yes.
Best,
Christian
Am 10.09.2015 15:53 schrieb "Rick Poleshuck" :
> My use is case is to read from a JMS queue and update two different jdbc
> tables with the same datasource. On failure of either update, both database
> actions should be rolled back and the message should be sent to a jms
> de
Is the dataSource configured in your context?
Best,
Christian
Am 10.09.2015 13:56 schrieb "arnaud" :
> Hello,
>
> Id'like to use a dynamic datasource with the camel-sql component but it's
> not woking as I expected:
> After a search on the forum, I have found a topic "Dynamic DataSource for
> SQL
Hi Claus, it works very well with a non-dynamic route. Thank you :-)
Btw, I also tried jetty as a producer compared to ahc. Jetty component
threw a lot of exceptions during the load test, whereas ahc worked
flawlessly.
Les
--
View this message in context:
http://camel.465427.n5.nabble.com/J
Hello all,
I am looking for a way to have a different redeliveryPolicy in Case the HTTP
statusCode is '503'.
I guess, I could do a try/catch finally every time I make a HTTP-Request. My
hope was to make that switch at one position, for all routes.
Does anyone have a thought on this problem.
This
Sorry, not sure if you are suggesting the same, but IMHO there should be
a way to optionally delegate to the underlying REST DSL consumer to
handle OPTIONS, even though it won't be for the purpose of starting a route.
Specifically, in CXF JAX-RS we have a very good CORS filter, I'm
presuming oth
I looked through the Splitter class and the streaming flag seems to decide
between using an Iterable directly or saving all entries of it into a list.
So as long as parallel processing is not active, it lookes like the sub
messages should still be in order, regardless of stream or not. I don't know
Hi,
Do you think that its is possible to reply to an OPTIONS request with Camel
REST DSL ?
When swagger ui sends a POST/PUT/DELETE request and that a different http
server issue the request, then it will first send an OPTIONS preflight
request (https://github.com/swagger-api/swagger-ui/issues/44,
Thanks for your reply Claus.
My fisrt try was with this method :
from("direct:create")
.setHeader("dataSource", simple("myDynamicDataSource"))
.to(simple("sql:insert into customer(firstname, lastname)
values(:#firstName, :#lastName)?dataSource=#${header.dataSource}")