Well I found myself something already better. Using java module instead of ejb module works fine with JBoss. So im my application.xml file I put something like
If I understand this method is not portable but anyway, at least it works and does not lock the jars.
Is it possible for you to post your META-INF/manifest.mf for your EJB jar to see how you have the Class-Path entry setup?
I posted a question http://www.jboss.com/index.html?module=bb&op=viewtopic&t=73214 about a standard way of deploying the EAR with dependent "utility" jars and was hoping to seee your example.
I am running into this exact problem except that I need to be able to support both Weblogic and JBoss. For years we've been supporting Weblogic using the manifest Class-Path option. Now we've added support for JBoss (on both Windows and Linux) in an exploded folder deployment.
I am in the process of trying to run the tests on Linux. As far as Windows is concerned, it is broken. I can fix it by moving the entries out of manifest Class-Path and into the application.xml as java modules BUT unfortunately this break Weblogic!!!
I'd really like to keep our deployments consistent across the board for the app server and the OSs being used.
In the mean time, the EJB spec has included a portable solution to this problem. JBoss 4.2.x is compatible with this new standard. Just put your jars in your.ear/lib
It is a bit like putting jars in yourapp.war/WEB-INF/lib except that they are loaded in the class loader of the ear. You will find more info googling.