Add ManagementObjectStrategy to SPI to allow customization of actual underlying
mbeans registered by Camel
----------------------------------------------------------------------------------------------------------
Key: CAMEL-4156
URL: https://issues.apache.org/jira/browse/CAMEL-4156
Project: Camel
Issue Type: Improvement
Components: camel-core, jmx
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Priority: Minor
Fix For: 2.8.0
When Camel registers MBeans in JMX it uses a lifecycle strategy for that, eg
the lifecycle strategy is triggered when X is added/remove to Camel. The JMX
supported lifecycle strategy is DefaultManagementLifecycleStrategy. That class
has some private code that creates the actual MBeans being used when
registering mbeans.
So far we have a pluggable SPI for defining ObjectName for the mbeans
(ManagementNameStrategy), so you can control that if you want.
Likewise we should have a pluggable SPI for the logic that creates the mbean to
be used. It should be named: ManagementObjectStrategy.
We should then move the private logic from DefaultManagementLifecycleStrategy
to a default implementation of that new SPI.
This makes it easier for end users and Camel itself to register new mbeans, and
reusing as much default code from Camel out of the box.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
