[
https://issues.apache.org/jira/browse/CAMEL-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968481#action_12968481
]
Guillaume Nodet commented on CAMEL-3398:
----------------------------------------
This issue seems much more complicated than it seems.
The reason is that in order for the camel blueprint namespace handler to find
the dependencies (such as components, etc...) so that the route will wait until
components are available, the handler does initialize the
CamelContextFactoryBean while the handler is parsing the xml. The bad effect
is that beans that are declared after the camel context won't be available yet
in the blueprint metadata registry.
I need to investigate a work around for that.
> Automatically imported beans are not taken into account in camel-blueprint
> (InterceptStrategy, LifecycleStrategy, etc...)
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-3398
> URL: https://issues.apache.org/jira/browse/CAMEL-3398
> Project: Camel
> Issue Type: Bug
> Components: camel-blueprint
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Fix For: 2.6.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
