Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Mon, 2 Apr 2012 11:53:22 +0000 (UTC)
From: "Christian Schneider (Created) (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: 
 <1227523662.273.1333367602711.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (KARAF-1302) Replace MBeanRegistrer with aries jmx
 whiteboard and remove .management modules
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Replace MBeanRegistrer with aries jmx whiteboard and remove .management modules
-------------------------------------------------------------------------------

                 Key: KARAF-1302
                 URL: https://issues.apache.org/jira/browse/KARAF-1302
             Project: Karaf
          Issue Type: Improvement
    Affects Versions: 2.2.5
            Reporter: Christian Schneider
            Assignee: Christian Schneider
             Fix For: 3.0.0


Currently we have a management module for each feature (like bundle or package) and use our own MBeanRegistrer class to install the mbean into the mbean server. 

This ties our management modules to the MBeanRegistrer. Additionally the setup of the MBeanRegistrer class reqquires that we install a service tracker for the MBeanServer and hook the register and unregister methods.

I propose to use a much simpler aproach. Aries JMX Whiteboard allows to register mbeans by just registering them as a service for an interface of *MBean and adding a property jmx.objectname. This has the advantage that our management bundles do not need a special dependency and the setup using the whiteboard pattern is well known from e.g. servlets.

As the MBean registration is passive then we can also make our module structure simpler. We can move the mbean code and setup into the core module. When the jmx whiteboard extender is not present the mbean code stays passive. As soon as the management feature is activated the mbeans become active.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira