[CAMEL-5712] BlueprintCamelContext should not get started in the init() method but later when the blueprint container is fully initialized

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.9.0, 2.10.0
• Fix Version/s: 2.9.5, 2.10.3, 2.11.0
• Component/s: camel-blueprint
• Estimated Complexity: Moderate
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 18/Oct/12 12:41
• Updated: 24/Oct/12 08:09
• Resolved: 18/Oct/12 19:43

Description

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.

Issue Links

• relates to: CAMEL-5738 HttpConnectionManager configuration is not injected correctly when using blueprint