The way I deploy the jars(ejb3s) are the simplest way. Jar the classes and rename it to .ejb3(maybe not necessary) and copy them to deploy directory. Restart JBoss to pick them up. I also think JBoss should use one classloader per ejb3 file. But seems not true in this case. Here is an answer I got from Jboss Forum: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=81729
Unless you specify otherwise via the <loader-repository> element in jboss.xml, all classes in .jar (or .ejb3) files will be loaded into the same root classloader repository. You can use the <loader-repository> element to create child repositories per deployment - classes loaded into child repositories will not be visible outside of the particular deployment.
Did they change the implementation recently?
[ April 25, 2006: Message edited by: Yuan Ye ]