> >Why not? Aren't DynamicMBeans easier to work with? I am actually a little
> >confused about the different types, short of the basic MBean that
> >implements a mgmt interface.
> >
>
> NO they are harder to implement. A dynamic MBean has to explicitly export
> all of it's managment interface. There is no *MBean interface class
> required. But this means you have to code in all that info that would have
> gone into the *MBean interface.
How about writing a simple abstract DynamicMBean which would use reflection
to get the mgmt interface. Or I think the Jetty JMX stuff exposes methods
to the subclass which allow it to specify arrays of strings for attributes
and operations, which the superclass would then use with reflection to
generate the correct information.
Or am I way off?
> >Why do you need the interface for dynamic?
>
> Because writing the MBean interface file is easier than implementing a
> DynamicMBean. This aproach though alows me to allso add description info to
> my MBean interface (only available with DynamicMBeans).
But once there is a common abstract to sub-class or a concreate wrapper
(that would proxy to an object), that seems like it would be easier than the
interface as well as provide more functionality.
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development