[ 
https://issues.apache.org/jira/browse/CAMEL-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-5876.
--------------------------------

       Resolution: Not A Problem
    Fix Version/s: 2.11.0
         Assignee: Claus Ibsen

This is as designed, when autoStartup=false, on <camelContext> then all routes 
is not started etc. You need to start Camel first.


                
> autoStartup=false in camelContext misbehaves
> --------------------------------------------
>
>                 Key: CAMEL-5876
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5876
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.10.2
>         Environment: Spring 3.1.3 based WebApp, camelContext and route 
> defined in webapp-servlet.xml, camelContext to be started in a bean
>            Reporter: Markus W Mahlberg
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.11.0
>
>
> {code:xml|title=webapp-servlet.xml||borderStyle=solid}
> ...
>     <camel:camelContext id="MyCamelContext" autoStartup="false">
>         <camel:route id="testroute">
>             <camel:from uri="timer:test?period=5s">
>             </camel:from>
>             <camel:log message="Consumed from timer"/>
>         </camel:route>
>     </camel:camelContext>
> ...
> {code}
> When set up like this, the route {{testroute}} is not started when the 
> camelContext is started, even when {{autoStartup="true"}} is explicitly added 
> to {{testroute}}.
> What I would expect is that the route is started automatically when 
> camelContext is started, as long as the route has no {{autoStartup="false"}} 
> property, since {{autoStartup=true}} is the default behavior for routes as 
> far as I understand the docs.
> If the current behavior is the intended one, the reversion of the default 
> behavior of routes should be pointed out in the docs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to