[
https://issues.apache.org/jira/browse/CAMEL-12087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475842#comment-16475842
]
Claus Ibsen commented on CAMEL-12087:
-------------------------------------
Do we really see this problem still? I can understand the lifecycle circular
issue you talk about, eg CamelContext is being created itself, and then some
custom bean is inject that is supposely camel context aware that gets a null
camel context as its not ready yet.
But that custom bean still need easy access to CamelContext. Passing in null
would be bad.
Maybe there is a way to register those beans on camelcontext in a temporary
list that they should have camel context injected later. And then CamelContext
will inject itself later in its doStart lifecycle.
> camel-core: WARN No CamelContext defined yet so cannot inject into bean
> -----------------------------------------------------------------------
>
> Key: CAMEL-12087
> URL: https://issues.apache.org/jira/browse/CAMEL-12087
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot
> Affects Versions: 2.20.3, 2.21.1
> Reporter: Luca Burgazzoli
> Assignee: Luca Burgazzoli
> Priority: Minor
> Fix For: 2.20.4, 2.21.2
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
