[
https://issues.apache.org/jira/browse/ARIES-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler closed ARIES-260.
--------------------------------
Resolution: Abandoned
> Reconsider synchronous MBean registration/unregistration
> --------------------------------------------------------
>
> Key: ARIES-260
> URL: https://issues.apache.org/jira/browse/ARIES-260
> Project: Aries
> Issue Type: Bug
> Components: JMX
> Reporter: Thomas Diesler
> Assignee: Adam Wojtuniak
> Priority: Major
>
> Currently if you do
> Bundle bundle = context.installBundle("org.apache.aries.jmx.jar");
> bundle.start()
> BundleStateMBean mbean = MBeanProxy.get(server, objectName,
> BundleStateMBean.class);
> mbean.listBundles();
> This might fail because the MBeans may not be registered when bundle.start()
> returns.
> To compensate this effect a client will have to do some
> server.isRegistered/timeout logic or perhaps some more complicated
> notification logic.
> IMHO, MBean registration should not be treated differently to osgi service
> registration i.e. it should be complete when Bundle.start() returns.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
