[
https://issues.apache.org/jira/browse/CAMEL-5451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved CAMEL-5451.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.10.1
2.9.3
> Camel-Blueprint should wait for camel-core to be started since there is a
> strong dependency
> -------------------------------------------------------------------------------------------
>
> Key: CAMEL-5451
> URL: https://issues.apache.org/jira/browse/CAMEL-5451
> Project: Camel
> Issue Type: Bug
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Fix For: 2.9.3, 2.10.1, 2.11.0
>
>
> When a camel/blueprint bundle is started without camel-core being started
> previously, there is a problem where the camel context factory bean tries to
> access the {{properties}} component, which is only available when
> {{camel-core}} is started.
> We need to ensure that the blueprint definitions created by the namespace
> handler also contains the needed reference to the {{properties}} component in
> order to make sure that blueprint will always wait for {{camel-core}} to be
> started (and the properties component actually available) before initializing
> the camel context.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira