As an ugly temporary hack to get it to compile I just copied the jars to the
old locations so that the IDE would work.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3937821#3937821
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mo
I did some checking in the code.
In EJB3Deployer there is a method called accept. This method does some simple
checks to see if something has the possiblity of being an ejb3 jar and if it is
it exits quickly. If it can't determine if it's an ejb3 jar it eventually calls
hasEjbAnnotation which s
The structure of the ear looks like this:
meta-inf/application.xml
module1.jar
module2.jar
...
module14.jar
lib1.jar
lib2.jar
...
lib20.jar
The application.xml contains a list of all the modules. Nothing special there.
The only thing interesting for each module is in the manifest there is a
Cla
I encountered a performance problem when deploying a very large .ear in jboss
4.0.4rc1 with ejb3 installed.
My ear contains 14 modules in it and many libraries. Each module has a manifest
that has a Class-Path that references other modules, and some shared libraries
in the ear.
Deploying it to