[
https://issues.apache.org/activemq/browse/CAMEL-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-2933.
--------------------------------
Resolution: Won't Fix
Lets keep it as is. The JMX MBeanName is using an easy to use default name so
management tooling can easily attach listeners if they want.
However end users need to enable notification by registering
{{JmxNotificationEventNotifier}} as an event listener.
> JMX notifications from JmxEventNotifier should be moved to be exposed on
> ManagedCamelContext instead
> ----------------------------------------------------------------------------------------------------
>
> Key: CAMEL-2933
> URL: https://issues.apache.org/activemq/browse/CAMEL-2933
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core, jmx
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.5.0
>
>
> Currently you need to enlist JmxEventNotifier to have JMX event notifications.
> It's much more intuitive that these notifications is exposed from the
> existing CamelContext MBean.
> Then end users dont have to remember to enlist the JmxEventNotifier, as they
> notifications is provided out of the box.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
