camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Anstey (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-770) allow a Spring Camel Context to be booted up just to extract the route defintions (camelContext.getRouteDefintions()) but not to actually process any routes
Date Thu, 14 Aug 2008 14:25:52 GMT

    [ https://issues.apache.org/activemq/browse/CAMEL-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44966#action_44966
] 

Jonathan Anstey commented on CAMEL-770:
---------------------------------------

Ah well, I'm pretty sure this is OK then :)

For a quick test, just run 'mvn camel:run -DshouldStartContext=false' on the camel-spring-example
- no routes will be started.

This one was really meant to be used with http://issues.apache.org/activemq/browse/CAMEL-769
IIRC.

> 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.


Mime
View raw message