RE: XML configuration of MBeans (extended MLet file)

Hi,

> Have you thought about using the java.beans package for this?  I'm 
> thinking you could maybe use its XMLEncoder and XMLDecoder, and its 
> Statement and Expression classes.  I admit I haven't studied 
> this closely.

I have read an introductory article for about long term persistence of javabeans, and thought about it a little bit.
I discarded it (for now) to be able to support JDK 1.3.

> I also don't understand the relation to MLets.  Is the idea 
> that MX4J's 
> MLet will be able to understand this extended file?  Or that 
> MX4J will 
> have an implementation-dependent subclass of MLet that does?

Actually it is a different class, not subclass of MLet, called ConfigurationLoader.
The classloading bits have to be cleaned up, for sure, but my idea is to use an MLet in the implementation to load the classes, with a syntax similar to MLet's for specifying URLs for the code.
That MLet can be instantiated outside (to set properly its parent classloader and CLR delegation), and feeded to the ConfigurationLoader. If it is not feeded, the ConfigurationLoader instantiates this MLet.
I am still not sure about using MLets, however. 
I have seen many times people subclassing and making an MBean out of URLClassLoader, and use that instead of MLet. Would be nice if ConfigurationLoader could take a ClassLoader to load classes, but ClassLoaders are not modifiable after created (no addURL() method).

I think such a syntax will be helpful, what are your ideas ? 
Have you (the jmx team) ever had the need for such an extended syntax ?

Regards,

Simon


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php