JBossMX has more-or-less copies of ServiceLibrary ==
UnifiedLoaderRepository and UnifiedClassLoader.  However jboss is still
using its own copies.

I've just removed the raison d'etre for MBeanClassLoader since I
implemented a different way of managing class-to-mbean dependencies.  I'm
wondering if it is OK and time to move to using the jbossmx loader
repository, and how to do it.  The dependency stuff I added requires the
ServiceLibraries to emit notifications when a class is removed, and it
should probably also notify when a UnifiedClassLoader is added.

So, my questions:

- Can we safely use jbossmx classloading? Will this require jboss to run on
jbossmx? Is this OK?

- How can we add these notifications to the UnifiedLoaderRepository? How
can an mbean register to receive them? Is the UnifiedLoaderRepository
supposed to be registered as an mbean? I don't see it at the moment.

- If it is not OK to move to jbossmx classloading, how would I load mbeans
without using the MBeanClassLoader?

Thanks
david jencks

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

Reply via email to