This is supported in jboss4, it hasn't been
backported to jboss3
So does that mean that putting other service in will not work in 3.x?
I have the additional problem where my mbean cannot find a utility class that is in server/default/lib even though I put in the deployment descriptor.
What am I doing wrong?
You shouldn't need to do the last part,
conf/jboss-service.xml already loads those jars.
I don't know what you are doing wrong without
For the if you are trying to specify
a dependency on a class it won't work in 3.x,
you can use the statement to load
the sar, but it is probably better to include both
services in the same sar.
I have found the problem with the class not being found. The class that it complained about was in the lib directory, but another class on which it depended wasn't. The other message didn't mention the missing class so it was a bit confusing...
I'm specifying a dependency on another mbean e.g. my.domain:service=MyService. It seems to work as they have always loaded in the correct order, so far at least...
Similar to Alwyn's problem, I found that a missing class was reported although that particular class was actually present. Adding another jar file to the lib directory fixed the problem.
So, I suspect, at least in some cases, there is a bug in reporting which class is not being found.
To anyone experiencing the NoClassDefFoundError, try adding jar files on which that class depends. The error message may go away.