>
>
>Well, my idea was that since Containers are mbeans already, why not
>transform the dd's to mbean config.  I'm still thinking about how to best
>deal with subsidiary objects.  I'm thinking if all the subsidiary objects
>are javabeans they can be constructed easily from xml, through jaxb or
>other ways.
>
I am still not sure this is a good idea.  Doing this will force MBeans 
to expose setters for all config, which may not be the proper admin 
interface for the bean.

Why not a pass the MBean an object that represtents its config?  Then it 
could choose what to expose.  Or how about a mix between the two... how 
I don't know.  This would allow config for black-box components and 
provide a rich interface for integrated components.

For example, could generate an object from xml (or handroll) then if the 
bean has a method to invoke and take the config object call it and your 
done, else do attrib set on each element.  This will only work with a 
flat config namespace though.

Or for the most adaptability, provide a mechanism to map config to mbean 
attributes/operations.

--jason


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to