aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r863307 - in /websites/staging/aries/trunk/content: ./ modules/jmx.html
Date Mon, 27 May 2013 14:16:40 GMT
Author: buildbot
Date: Mon May 27 14:16:30 2013
New Revision: 863307

Staging update by buildbot for aries

    websites/staging/aries/trunk/content/   (props changed)

Propchange: websites/staging/aries/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Mon May 27 14:16:30 2013
@@ -1 +1 @@

Modified: websites/staging/aries/trunk/content/modules/jmx.html
--- websites/staging/aries/trunk/content/modules/jmx.html (original)
+++ websites/staging/aries/trunk/content/modules/jmx.html Mon May 27 14:16:30 2013
@@ -321,7 +321,16 @@ START LEVEL 1
 <h2 id="blueprint-integration">Blueprint Integration</h2>
 <h2 id="whiteboard-support">Whiteboard support</h2>
+<p>The JMX Whiteboard support bundle allows registration of JMX MBeans through the
OSGi service registry. As a prerequisite
+the Apache Aries JMX Whiteboard Bundle has to be installed.</p>
+<p>Once this is installed, register your services with
+the <code>jmx.objectname</code> service registration property. This is either
a JMX <code>ObjectName</code> or a single String. The value is
+used as the JMX Object Name to register the MBean. If the property is of some other type
a message is logged and the
+MBean is still registered if the service implements the <code>MBeanRegistration</code>
interface and the implmentation provides the
+actual JMX Object Name to use for the registration.</p>
+<p>The name of the service as which the MBean service is registered is ignored by the
+<p>The service object, though, must be a valid JMX MBean: It has to either implement
the <code>DynamicMBean</code> interface or implement
+an interface whose name is the object's (simple) class name with the <code>MBean</code>
             <!-- Content -->

View raw message