I'm not sure I understand the question.
The MLet class is a URLClassLoader.
It will use the system classloader (classpath)
But if the class is not found, it will load from the
Perhaps you can explain your problem in more detail?
Well, I have written a service for JBoss in form of a MBean.
If I want to debug it, I have to start JBoss in debug-mode. The code, wich should be debuged, here the MBean code, must be accessable by the debugger (here Eclipse). So I have to put the directory, where the code is, to the classpath of JBoss. However, if JBoss starts,
occurs. If I put the code in form of a jar-file in the lib/ext directory of JBoss and remove the directory containing the unzipped code from the classpath, the error does not appear and the service is started fine. However, the debugging is not possible know.
I hope, you know, what I mean and I hope you can give me an answer.
The class you report is in jboss.jar in lib/ext
this is loaded by the JBoss classloader.
If you add something to the System classpath, it
cannot see anything in the JBoss classloader.
I don't know anything about Eclipse. I would be surprised
if a debugger only lets you debug code on the classpath.
I have done a ClassPathExtension in jboss.conf and it works everthing fine.
I'm having a similar problem in JBoss 3.0, but there is
no jboss.conf to extend the classpath. How can you do this
in JBoss 3.0????