Can somebody confirm that there is a bug in the implementation of the <loader-repository> functionality for ears in combination with the use of XMBeans.
Using JBoss 3.2.0RC2, I find scoped class loading to be working fine for e.g. Standard MBeans (the SAR inside a scoped EAR) and XMBeans to be working nicely when not trying to scope them.
Combining these wonderful features consistently results in:
16:22:57,290 WARN [ServiceConfigurator] Failed to complete install
java.lang.ClassNotFoundException: No ClassLoaders found for: com.globalros.broadcast.BroadcastServer
at org.jboss.mx.loading.LoadMgr.beginLoadTask(LoadMgr.java:155)
at org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:161)
at org.jboss.mx.loading.UnifiedLoaderRepository3.loadClass(UnifiedLoaderRepository3.java:144)
at org.jboss.mx.loading.UnifiedLoaderRepository3.loadClass(UnifiedLoaderRepository3.java:489)
at javax.management.loading.DefaultLoaderRepository.loadClass(DefaultLoaderRepository.java:78)
at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:825)
at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:266)
at org.jboss.system.ServiceCreator.install(ServiceCreator.java:103)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:155)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:118)
at org.jboss.system.ServiceController.install(ServiceController.java:225)
at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source)
(Actually, this stack trace is the result of deploying under the CVS HEAD for JBoss 3.2.0RC3 ).
Thanks, Jurjan-Paul Medema
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
