classpath issues

[acxsjones]

I have a mbean that will be making an external call. Everything works fine when I put the third party jar in my sar.

The next need, is to allow users of this mbean to change some of the params before deploying. I want to use your same pattern of packing the code in a jar and the test-service.xml with a

<classpath codebase="lib" archives="myMBean.jar, thirdparty.jar"/>

It sees the classes in myMBean.jar but not in thirdparty.jar

[achase]

Did you ever get this resolved? I am having very similar issues where the 3rd party jar file seems invisible no matter where I put it.

[raja05]

1. If the codebase is ".", then the archives are taken from the root of ur particular deployment, i.e. xxx.sar/<archive-path>
2) If the codebase is not ".", then the path is taken from the server.home.url which is typically jboss_home/server/default.

so if you put ur entry as
<classpath codebase="lib" archives="xxx.jar,yyy.jar", you should typically be putting it in the jboss_home/server/default/lib directory. As far as the MBean itself is concerned, i think it looks it the jar in the SAR for the MBean but not for external jar files.