Hi, Danny.
At least part of the problem is that the application.xml specifies the AEV-base library as an app client. That's what the <java> element in application.xml means. The <java> element does not mean that the JAR is a library.
Various packaging and class path decisions are driven by the module types, so my first suggestion is to fix that and then see what happens from there. Library JARs should reside at the /lib directory within the EAR or at whatever location in the EAR is specified by the <library-directory> element in the application.xml descriptor. (The /lib value is the default if none is specified.)
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=229078