Really just trying to make sure I understand how the configuration works. If
I auto configure activemq with Spring Boot, I have noticed that an activemq
component is also created in the camel context. Is Spring Boot creating
this component or the camel context?
So when I need to have a
On Fri, Dec 4, 2015 at 6:01 AM, Randy Bowen wrote:
>
> As of version 2.16.0, the camel-elasticsearch component appears to hard-code
> the configuration of the client.transport.sniff parameter for the
> TransportClient to “true”. This causes transport connections to fail in
What version of Camel do you use? And can you show all your Camel
routes and configuration
On Thu, Nov 26, 2015 at 9:14 AM, Scisci wrote:
> Hi,
> after a bit of investigation I've found when the aggregation not end.
> If the last item in the split throw an error it will
Since you do not use cache consumer, you likely need some kind of jms
connection pooling to speed up this. Some JMS clients has that
built-in, others you need to configure this from either a pool they
provide, or you can use the generic jms pool from spring-jms.
And depending on whether you use
You can use camel-jetty8 as that is the old version of jetty
On Wed, Dec 2, 2015 at 10:43 AM, kalber wrote:
> Setting useContinuation=false solves my probelm.
>
>
>
> -
> kh
> --
> View this message in context:
>
That is not really the point with the camel file components.
That you use it to delete arbitrary files.
It was for consuming, processing the files, and then afterwards decide
what to do with that original file, such as delete / move etc.
If you want to delete some file, there is plenty of java
Hi, I have a question:
We have two camel/servicemix instances. One for tests and one for production
use. Also, for a route in Test, from is usually a different location
compared to Production. Same with the final destination.
I'd like to build only one .WAR with maven that I can deploy to both
Hi,
We have exactly same requirement.
On tomcat startup, we push some variable to point our property file
-Dmyprops.home=/etc/myfile.properties
And in the spring declaration we do :
file:${myprops.home}
And next you can use regular spring
Hi,
Spring Boot creates connectionFactory bean for you. It is named
"jmsConnectionfactory" [1]. In order to wire Camel with Spring Boot AMQ
support, you have to refer that bean from JMS component URI:
from("jms:queue?connectionFactory=#jmsConnectionfactory").to(...);
Simple as that :)