Setting classpath on MBean when using different loader respo

[rfoyle]

I have changed my classloader repository in jboss-app.xml for my ear file because of class versions. The class used to load fine until I made this repository change. Assistance or suggestions would be greatly appreciated!

-Rich
[e-mail]

[jboss-app.xml]
<jboss-app>
<loader-repository>repository:application=myEar.ear</loader-repository>
</jboss-app>

My problem is that my ear contains a .sar for my mbeans. When JBoss launches it can not find the actual class

Jboss complains:
2002-08-21 13:04:09,890 DEBUG [org.jboss.system.ServiceCreator] Class not found for mbean: user:service=myService

[user-service.xml]

[rfoyle]

I can look up my classes at through the JMX viewer

Here is what I see:
MBean Name: repository:application=myEar.ear
MBean Java Class: org.jboss.mx.loading.HeirarchicalLoaderRepository

It lists the Jars and Sars. And I can lookup the class in question which returns fine.

My problem is what to put in:
in the MBean descriptor file that is in my Sar file.

[davidjencks]

I don't think the classpath element will have any effect on this. It's possible that the scoped classloading isn't working properly for mbeans except in jboss 4, so you might try that and report the results.

[rfoyle]

Jboss 4? Didn't see anything on sourceforge or jboss.org regarding this version.

Are there other approaches that might work in the current release of JBoss? I need startup classes (mbean) and need to isolate some classes that run because of versioning/classpath issues... Again any help is greatly appreciated!

-Rich

[adrian.brock]

Didn't Scott fix this?

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/jmx/src/main/org/jboss/mx/server/registry/BasicMBeanRegistry.java?only_with_tag=Branch_3_0

The fix should be available when 3.0.2 is released
otherwise you'll have to get Branch_3_0 from CVS

Regards,
Adrian

[rfoyle]

Given that this fix is in a future yet to be *released* version. Is there a workaround that you could suggest?

Thanks,

Rich

[adrian.brock]

Checkout Branch_3_0 from CVS and build 3.0.2 yourself?

Or patch jboss-jmx.jar with the fixed version of the
registry mentioned above?

Regards,
Adrian