Yeah the routes are prepared during startup so it depends what the problem is.
You can add the routes using the java api, using addRoutes if you want
to add them one by one, and ignore any problems.
Though it does smell that you have a system where you do not care if
some part of it do not work.
Doesn't Camel try to resolve endpoint even if route isn't autostarted ?
If not, how can i start my route(s) only when my application's context is
started?
Thx
Arnaud
--
View this message in context:
http://camel.465427.n5.nabble.com/Prevent-FailedToCreateRouteException-to-cause-application-sto
Mark all routes to not auto startup, and then start them yourself one
by one from some Java code etc.
On Wed, Nov 25, 2015 at 3:23 PM, Brossard wrote:
> Hi,
>
> I am currently using Camel 2.16 in a web application, starting it with a
> *ContextLoaderListener* in my *web.xml*.
> Is there a way to
