camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (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
Date Sun, 24 Jul 2011 10:44:09 GMT
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.8.0, 2.7.2
            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

        

Mime
View raw message