Hi, I've renamed add/removeClassLoader to add/removeCL for external management of the repository. The MBeanServer uses add/removeClassLoader which ignore requests on UnifiedClassLoaders.
I fixed the handling of URLClassLoaders, although this approach won't support package private access across URLs in the same URLClassLoader. I've also added some guards where a URL is mistakenly registered twice. Previously, the CL was removed when the first of the duplicates was removed. I'll look at copying the jmx loading tests into the main testsuite. Regards, Adrian >From: "Scott M Stark" <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: <[EMAIL PROTECTED]> >Subject: Re: [JBoss-dev] BasicMBeanRegistry and class loader MBeans >Date: Sat, 10 Aug 2002 12:22:25 -0700 > >Look at fixing it in head as there the BasicMBeanRegistry has been >restored, >but the default has been changed to JBossMBeanRegistry. The design of >our JMX implementation class loading layer has to be geared toward JBoss >functionality and requirements. Accommodating whatever is required by the >JMX spec is necessary, but if one or the other requires a non-trivial >configuration, >it is the JMX spec behavior that should incur this burden, not the default >JBoss behavior. > >xxxxxxxxxxxxxxxxxxxxxxxx >Scott Stark >Chief Technology Officer >JBoss Group, LLC >xxxxxxxxxxxxxxxxxxxxxxxx >----- Original Message ----- >From: "Adrian Brock" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Saturday, August 10, 2002 11:44 AM >Subject: Re: [JBoss-dev] BasicMBeanRegistry and class loader MBeans > > > > Hi Scott, > > > > This is the specs/RIs mechanism for maintaining the LoaderRepository, > > although it is only implicitly mentioned in the javadoc for the > > DefaultLoaderRepository: > > "Keeps the list of Class Loaders registered in the MBean Server. It >provides > > the necessary methods to load classes using the registered Class >Loaders." > > > > The unified repositories are externally managed and hierarchical, > > so this behaviour is conflicting. > > I see you have already removed this code. > > > > This probably breaks the MLet processing. But then I think it > > was already broken, MLets are URLClassLoaders not UCLs. > > > > I'll take a look at fixing this without breaking bug #592346 > > > > Regards, > > Adrian > > > > >From: "Scott M Stark" <[EMAIL PROTECTED]> > > >Reply-To: [EMAIL PROTECTED] > > >To: <[EMAIL PROTECTED]> > > >Subject: [JBoss-dev] BasicMBeanRegistry and class loader MBeans > > >Date: Fri, 9 Aug 2002 12:11:41 -0700 > > > > > >When one registers an MBean that is a ClassLoader the >BasicMBeanRegistry > > >adds it to the the default LoaderRepository. This breaks scoped class > > >loading > > >of services, and it really seems to be out of the scope of >functionality > > >that the BasicMBeanRegistry should assume. Really I don't see why the > > >BasicMBeanRegistry should have any interaction with the >LoaderRepository > > >as all it is doing is adding and removing class loaders. > > > > > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >Jboss-development mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-development _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
