[
https://issues.apache.org/jira/browse/CAMEL-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-4263.
--------------------------------
Resolution: Fixed
> When using @EndpointInject or other bean initializers, then JMX should pre
> record those lifecycle events to enlist in JMX later when CamelContext has
> been enlisted
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-4263
> URL: https://issues.apache.org/jira/browse/CAMEL-4263
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, jmx
> Affects Versions: 2.7.2, 2.8.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.9.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/Camel-issue-with-JMX-Endpoints-disappearing-and-endpoint-injection-for-SEDA-tp4616624p4616624.html
> The problem is that when you use @EndpointInject, @Produce, @Consume etc. on
> beans then Spring / Blueprint triggers the CamelBeanPostProcessor which
> inject those details into the bean. But this process happens very early,
> before CamelContext is being started.
> And thus components/endpoints/etc is already been loaded/registered in
> registry.
> But they cannot this early be enlisted in JMX, as CamelContext has not yet
> been enlisted. So we need to pre record those events, and then enlist them
> after CamelContext has been enlisted in JMX.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
