2009/11/19 Rex Wang <[email protected]>: > 2009/11/19 Siqi Du <[email protected]> > >> I also feel it is not very graceful to use containerServiceId every >> time. In common cases there are several container services and a >> single extender service. Maybe it is better to distinguish the mbean >> for blueprint extender from the mbean for a blueprint >> bundle/container？ >> > There is no need to design such 2 mbeans, because you can not make any > operation on an extender. The intent here is to track the blueprint bundles > state. Please take the FrameworkMBean and BundleStateMBean as an example. > Thanks :-) > -Rex
Understood. Anyway, the blueprint-mbeans is really a plus for blueprint implementation so I hope it can be placed in Aries.
