On 26 February 2013 07:02, Justin Edelson <[email protected]> wrote: > Hi, > > > On Mon, Feb 25, 2013 at 4:24 AM, Felix Meschberger <[email protected]>wrote: > >> Hi, >> >> Am 22.02.2013 um 23:59 schrieb Ian Boston: >> >> > >> > Implementation >> > * MBeans are not that hard to implement with the OSGi Whiteboard, but >> > they have to be implemented. >> >> Right. Everyhting that has to be queried has to be implemented. The actual >> problem I see, is that a separate API is required, which in turn is good >> programming style anyway when doing services. Yet this API does not need to >> be exported because the JMX Whiteboard gets to it through the MBean service >> class (IIRC). >> > > The MBean API does not *need* to be exported but it *should* be exported so > that client applications can use it if they want to.
yup, the white board impl (Aries) looks at the service implemented property to see if it matches *MBean. If it does the service gets registered using the property jmx.objectname If extending a StandardMBean, the MBean interface being implemented is passed in the super constructor call and all the methods on the MBean interface are exposed to the MBean server. For JMX the interface doesn't need to be exported as its only the class internals that introspect it. Ian > > Justin > > <snip>
