[JBoss-user] EAR, EJB-JAR, and WAR with Dependant JARs

[Rod Macpherson]

I have an unpackaged war where the JSP pages find beans but the beans they delegate to cannot locate jars within the WEB-INF/lib or WEB-INF/classes directory. Place it in an ear (directory with a dot ear extension for example) and there is no problem. Placing the jars in the deploy directory also works as does the /jboss/server/default/lib in my case.  Hot deploy of individual ejb jars works great but shared jars have to go in /jboss/server/default/lib (or equivalent) where they cannot be hot deployed. Consequently you cannot hot deploy jars used across multiple tiers. You made the comment "who can live without this feature" referring to hot deploy of individual ejb jars and wars. I agree that this is an important feature but would extend that to shared utility jars during development. For me everything is copecetic except for the failure to find classes in an unpackaged war (in a dot war directory versus an actual file), the seemingly inoperable Class-Path in MANIFEST.MF and the inability to hot deploy a shared utility jar. I should hasten to add there could be some localized configuration issue but then several people report class loading problems. I will try and distill a succinct example that demonstrates the problems � and to elminate pilot error as the source of the problem :)   ----- Original Message -----   From: "Jee-Meng Ang" <[EMAIL PROTECTED]> Date: Sat, 14 Dec 2002 14:59:26 +0800 I have a question regarding the deployment of dependant JARs.  According to J2EE spec, EJB-JARs and WAR are able to refer to another JAR in the same EAR using the Class-Path property within the MANIFEST.MF files. But using EARs for deployment means that the development-deploy-test cycle take a long time due to the overhead in packaging and redeploying the EAR. This will discourage developers from doing incremental development. JBoss supports hot deploy of individual EJB-JARs and WARs.  Who can live without this feature.  However, can JBoss support reference of classes in other Jars from EJB-JARs and WARs through MANIFEST.MF?  If so, where should I deploy these dependant Jars?  And can the Jars be hot deployed just like the EJB-JARs and WARs?