[
https://issues.apache.org/activemq/browse/CAMEL-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44965#action_44965
]
James Strachan commented on CAMEL-770:
--------------------------------------
yeah - the use case really is to be able to boot up a camel context, look at
the route definitions - but then not have to actually activate the routing rules
> allow a Spring Camel Context to be booted up just to extract the route
> defintions (camelContext.getRouteDefintions()) but not to actually process
> any routes
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-770
> URL: https://issues.apache.org/activemq/browse/CAMEL-770
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: James Strachan
> Fix For: 1.5.0
>
> Attachments: maybeStartSpringCamelContext.patch
>
>
> To visualise routes its kinda handy to just boot up a Camel Context and check
> everything configures correctly, then get the route configurations - rather
> than having to actually start all the routes up.
> i.e. to check the configuration works - and to apply any Java / Scala / XML
> route creation code - but not actually start any routes processing
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
