> >By doing this we could create a subclass which would use introspection to
> >list all attributes and operations, for objects that want to be beans and
> >just what to expose all publics.
> >
>
> I see how this could be simpler in some cases... But in cases where you are
> using interface Inheritance, MBean interface files really shine. By
> extending another interface you are exposing those managment methods too.
> Plus it seems like you better compile time checking since the compiler will
> let you know if you miss typed something in the MBean interface file. Whith
> your approach above, you would not know if you missed typed anything until
> runtime.
Correct me if I am wrong, but with interfaces you can not support all of the
features of an MBean right? Which is why you had to implement any
DynamicMBean stuff.
This seems like a very poor design. I see your point though. I remember
reading some parts of the spec wrt interface inheritence. Short of the
ServiceMBeanSupport are we using this anywhere?
> >Dealing with the interface reminds me of c header files. In most cases the
> >MBean that I write want to expose all public methods, so when I add a new
> >one, update the sig or whatever, I have to keep the *MBean iterface upto
> >date. Note a big deal, but kinda tedious. If we are going to move to
> >dynamic mbeans to make better use of jmx (which I think is a great idea)
> >then why not expliot it to the fullest and make JBoss more maintainable and
> >easier to extend...
>
> I don't think that going one way or another will make a real impact on the
> maintanance or extensability of JBoss... If anything doing it either way
> will make it less understandable since we will be diverging from standard
> MBean type code in DynamicMBean code.
What do you mean "diverging from standard MBean type code"?
> >Sure, commit it.
> >
>
> ok.. will do in a few days...
Cool.
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development