[CAMEL-4263] 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

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7.2, 2.8.0
• Fix Version/s: 2.8.2, 2.9.0
• Component/s: camel-core, jmx
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 24/Jul/11 10:43
• Updated: 19/Sep/11 18:46
• Resolved: 24/Jul/11 12:54

Description

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.