|
From: Carlos Q. <car...@we...> - 2002-02-04 23:10:53
|
On Tuesday 05 February 2002 00:55, Dmitri Colebatch wrote: > > > @jmx:mbean defines things that are related to the spec. Its presence > > > indicates that a MyServiceMBean interface will be created for the > > > MyService class. the extends parameter specifies an interface for the > > > MyServiceMBean interface to extend. > > > > Ok, so @jmx:mbean will ONLY take a extends parameter, no name, no > > description > > sorry. no, @jmx:mbean does take a name and description parameter. And then what does the name parameter do? > > > > @openjmx:description defines things that are related to the openjmx > > > description adaptor class. The absense of it means that all defaults > > > will be followed for the openjmx description class. Its extends > > > parameter allows the description class to extend a specific class - > > > this class should itself extend the openjmx abstract description class. > > > If it is not there, and the MyService class extends FooService, then > > > the > > > > Is it that the class extends FooService or that the @jmx:mbean has > > parameter extends="FooService". The latter seems the correct to me > > sorry - yes, its if the @jmx:mbean has the extends paramter. my bad. > > > > MyServiceMBeanDescription class will extend FooServiceMBeanDescription > > > (are they the right class names?). If there is no > > > @openjmx:descriptione extends="" _and_ MyService doesn't extend > > > anything, then > > > MyServiceMBeanDescription will simply extend the OpenJMX abstract > > > description class (sorry - cant remember the name). > > > > it is MBeanDescriptionAdaptor > > ta > > cheers > dim |