Re: [jboss-cvs] jmx/src/main/org/jboss/mx/server/registry BasicMBeanRegistry.java

[Juha-P L. <jpl...@cc...>]

On Sat, 10 Aug 2002, Scott M Stark wrote:

> I can't see where this contract has to be mediated by the registry per
> any of the JMX docs. The only place registered class loaders show
> up in the JMX classes is javax.management.loadingDefaultLoaderRepository
> protected Vector loaders instance. This does not have to be all
> registered MBeans that also happen to be ClassLoaders as far as I
> can tell.

This behavior hasn't been stated explicitly in the spec so far, but will
be in the next 1.2 maintenance release. MBeans that are instances of
classloaders are added to the loader repository.

The registry is a logical place to do this. Therefore it makes sense the
basic implementation of the registry does this automatically. If you want
different behavior, just plug in another registry implementation.

>
> Define the use case your talking about here and we need a testcase for
> ensuring JMX spec behavior with regard to plugability of the loader
> repositories and exactly what the relationship to the registry is, if any.

I'm pretty sure that if you remove the hard coding for ULR in the JBossMX
implementation and change it back to DefaultLoaderRepository you will see
in our test suite that the change you made breaks at least some tests.

If I need to use classes from MLet A then that Mlet loader needs to be
present in loader repository. Otherwise DLR.loadClass(MLetAClass) will
fail with non-UCL based repository.

-- Juha