As promised, I tried my test application on 2.4.10. Using the EAR structure
below, I can deploy on both 2.4.10 and 3.x.
<root>
META-INF
application.xml
MANIFEST.MF
ejb
us_state_service.jar
lib
apogent-common.jar
eif-ejb.jar
</root>
As I noted earlier, the key was two-fold: 1) to use a manifest file in each
EJB JAR to specify the class path to library JARs, which I was already
doing; 2) to use a path relative to the EJB JARs instead of to the root of
the EAR file. Thus, use whatever structure works best for your application,
but always heed the aforementioned #2.
Again, many thanks to all who helped. I hope that the rest of the community
benefits as well.
Craig
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
