Hi Tim Iam against exposing MBeans outside JMX bundle. Lifecycle of all MBeans is managed by JMX bundle using MBeanHandlers and I think it should be this way. In your factory you are using framework MBeans but what will happen if you want to use compendium MBeans. They all created based on availability of compendium services which is managed inside JMX bundle. In such a case the outside user will have to manage those MBeans by himslef. Even he can't be sure if could get MBean from JMX could be not available at the time. Currently the best way to register MBeans in an external MBean server is to register the server as a service.
Regards, Adam Wojtuniak On Wed, Feb 3, 2010 at 4:21 PM, Tim Mitchell (JIRA) <[email protected]> wrote: > Add a factory class to allow the OSGi JMX MBeans to be registered in an > external MBean server > > --------------------------------------------------------------------------------------------- > > Key: ARIES-141 > URL: https://issues.apache.org/jira/browse/ARIES-141 > Project: Aries > Issue Type: Improvement > Components: JMX > Reporter: Tim Mitchell > Priority: Minor > Attachments: JMXFactoryPatch.txt > > Currently there is no way of accessing the Apache Aries MBeans in order to > register them in an external MBean server. I am proposing a factory class > that will be exported from the jmx bundle that will allow users to access > the internal MBean. > I have supplied a patch with my suggested class. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
