[SM-4123] Unexpected automatic EventNotifier attachment to CamelContexts

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 7.0.x
• Component/s: servicemix-camel

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

• Assignee: Jean-Baptiste Onofré
• Reporter: Ephemeris Lappis
• Created: 10/Jul/19 16:33
• Updated: 25/Mar/20 09:07

Description

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.