[
http://issues.apache.org/jira/browse/CONFIGURATION-237?page=comments#action_12449598
]
nicolas de loof commented on CONFIGURATION-237:
-----------------------------------------------
JMX has multiple way to expose application datas/features. This pacth only
includes a static MBean, this means the Class implements an interface with the
same name + MBean. Exported into a JMX Server, such a class will automagically
expose to JMX management methods (and/or javabean properties) defines by the
MBean interface.
I myself use Spring MBeanExporter to do the work :
<bean id="mbeanExporter" class="org.springframework.jmx.export.MBeanExporter">
<property name="beans">
<map>
<entry key="myApp:name=configuration">
<bean
class="org.apache.commons.configuration.reloading.ManagedReloadingStrategy"/>
</entry>
</map>
</property>
<property name="server" ref="mbeanServer"/>
</bean>
In fact, I don't know another way to expose a bean to a JMX MBeanServer, as I
did never had to do it programmaticaly...
Hope it make this more comprehensible.
> Contrib : managed reloading strategy
> ------------------------------------
>
> Key: CONFIGURATION-237
> URL: http://issues.apache.org/jira/browse/CONFIGURATION-237
> Project: Commons Configuration
> Issue Type: New Feature
> Affects Versions: Nightly Builds
> Reporter: nicolas de loof
> Priority: Minor
> Attachments: CONFIGURATION-237.patch
>
>
> This patch adds a reloading strategy based on management request, typically
> from a JMX console. The Strategy implements a MBean interface so can be
> exported as a JMX Managed bean with no code change.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
