Hi
See this link
http://camel.apache.org/running-camel-standalone-and-have-it-keep-running.html
And read the javadoc of the start method on CamelContext.
The start method is non-blocking, so you need some way to keep the jvm
running. As the links above talks about.
On Tue, Aug 12, 2014 at 3:50 PM, James Green james.mk.gr...@gmail.com wrote:
We're missing something fundamental here.
https://gist.github.com/jmkgreen/ed271348de66646a87be
I run this, I get the following in the logs:
https://gist.github.com/jmkgreen/91b89c32fe03ffb93ead
So we're wondering what we're doing that doesn't actually execute the route?
This comes out of a really simple standalone application we're writing with
Spring that does exactly the same - configures and starts Camel then exits.
In puzzlement we decided the above source couldn't possibly fail, but does
exactly the same!
Hope someone can point out an obvious error.
Thanks,
James
--
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
