You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicemix.apache.org by "Ephemeris Lappis (JIRA)" <ji...@apache.org> on 2019/07/10 16:34:00 UTC

[jira] [Created] (SM-4123) Unexpected automatic EventNotifier attachment to CamelContexts

Ephemeris Lappis created SM-4123:
------------------------------------

             Summary: Unexpected automatic EventNotifier attachment to CamelContexts
                 Key: SM-4123
                 URL: https://issues.apache.org/jira/browse/SM-4123
             Project: ServiceMix
          Issue Type: Bug
          Components: servicemix-camel
    Affects Versions: 7.0.x
         Environment: Same behavior on :
 * Camel 2.16.5 / SMX 7.0.1
 * Camel 2.17.0.redhat-630187 on Fuse fabric8-karaf-1.2.0.redhat-630187
            Reporter: Ephemeris Lappis


We try to provide a shared EventNotifier as an exposed OSGi service from a bundle. This bundle has a simple Java class that implements the EventNotifier interface, and a blueprint to expose it as a service.

Other bundles are designed with a simple blueprint with a reference to the previous service, and a CamelContext and its routes.

Two issues 
 * Wwith or without a reference to the service in the blueprint, all the CamelContext are attached to the EventNotifier.
 * All other EventNotifier that may be instantiated by a bundle (bean in the blueprint), are ignored, not registered, and they don't receive events.

It seems that the simple presence of the EventNotifier "as a service" registers it automatically in all the deployed CamelContext.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)