Hi there,
My suggestion would be to host your camel application in a container such as
Karaf/SMX and run it as a OS service. This will allow you to restart your
container automatically on a failure etc.
It would be advisable to make use of Transactions in your routes and a
persisted transport mec
I don't want to be nagging, but personally I wouldn't go down the route
(hmm...nice play of words) of
creating routes dynamically from the application. Personally I would
stick to having the route in my
source code and therefore tagged and released and tested etc.
Generating the config can only
Thanks for the clarification Charles & Andreas, I understand. I hope there
is a roadmap for this in Camel 3.0 .
Claus, This is the best available solution as of now, which I consider using
it.
Cheers,
Guru
gnanaguru.com
--
View this message in context:
http://camel.465427.n5.nabble.com/We
Ad 2)
spring dsl is just a xml file so you can write that to disk. And then
on restart you can load the routes from the xml file(s).
See also
http://camel.apache.org/loading-routes-from-xml-files.html
On Thu, Sep 5, 2013 at 7:16 PM, Gnanaguru S
wrote:
>
> Hello,
>
> I have two file endpoints, I
Hi,
in theory you could configure a generic camel route between two files
and use a property resolver
to route from file1 to file2. Then its a matter of sticking the
properties into the right location on disk
and initialize your Camel route accordingly on startup.
This having said, the JVM co
Guru,
A CamelContext is a java object which is not persisted or replicated
between different JVM. So this is not possible to achieve what you would
like to do. The question here is not the CamelContext or RouteBuilder
object but what you transport (= files). They must be persisted (using
ActiveMQ,
