Claus Ibsen created CAMEL-5712:
----------------------------------
Summary: BlueprintCamelContext should not get started in the
init() method but later when the blueprint container is fully initialized
Key: CAMEL-5712
URL: https://issues.apache.org/jira/browse/CAMEL-5712
Project: Camel
Issue Type: Bug
Components: camel-blueprint
Affects Versions: 2.10.0, 2.9.0
Reporter: Claus Ibsen
Priority: Critical
Fix For: 2.9.5, 2.10.3, 2.11.0
The init() method in BlueprintCamelContext should not call maybeStart(). but
instead should be started when the blueprint container is done doing all its
dance and initialization.
For example Spring sends on ContextRefreshedEvent when its done.
We need something similar for blueprint to tell us when its done doing its
initialization et all.
The problem is that the CamelContext should not be started until all that other
stuff is initialized as well.
--
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
