aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <>
Subject [jira] Resolved: (ARIES-430) Whiteboard registration support for JMX DynamicMBeans
Date Tue, 02 Nov 2010 21:09:09 GMT


Guillaume Nodet resolved ARIES-430.

       Resolution: Fixed
    Fix Version/s: 0.3

I've copied the sling code and integrated into the aries jmx component.

> Whiteboard registration support for JMX DynamicMBeans
> -----------------------------------------------------
>                 Key: ARIES-430
>                 URL:
>             Project: Aries
>          Issue Type: New Feature
>          Components: JMX
>            Reporter: Felix Meschberger
>            Assignee: Guillaume Nodet
>             Fix For: 0.3
> As proposed on dev [1] I have hacked together a small piece of code which implements
support for the whiteboard pattern for registering MBeans with MBean servers.
> The code is in my Sling whiteboard at
but is intended to be added to the Aries JMX functionality.
> The single-class implementation picks up DynamicMBean servies registered as "".
Each such service is registered with each registered MBeanServer service (similar to how the
framework MBeans are registered by jmx.core). The JMX ObjectName can either be provided with
a "jmx.objectname" service registration property (String type) or the DynamicMBean may implement
the MBeanRegistration interface in which case the ObjectName is provided by the preRegister
method during registration.
> This is just a first hack which has not really been tested but mainly serves to show
the idea. It is currently implemented as a Declarative Services component but may as well
be implemented as a regular class using ServerTracker instances and instantiated by the BundleActivator
(which may be a good idea to make this as widely usable as possible - for example in Sling
we don't currently use Blueprint, so a Blueprint based implementation would be a no-go for
us ;-) )
> If there would be interest in this, I would try to test and validate this piece with
the hopes to get a release soon (may be released independently, hint hint ;-) )
> [1]

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message