[Kurtis Williams]

I’ve got a strange one in the package deployment for Tomcat 5. When I do a n “Exploded Archive deployment”, everything deploys fine, but when I deploy the exact same application using “Packaged Deployment,” the WAR file does not contain the XML files from my application (except the Web.xml, which is included).

I expected that the packaged deployment would be the same as the exploded deployment.

Thanks!

[Riyad Kalla]

cardsharp,
Can you give us the Build IDs of Eclipse (Help > About) and MyEclipse (Window >Preferences > MyEclipse), so please explain your project structure:
project root dir
src dir
output dir
webroot dir

also tell us where the XML files are located.

[Kurtis Williams]

The project is composed of a Web project and a secondary “shared” project that has classes that are re-used in several web apps. The XML files that are missing are contained in the required “shared” project. The project structure is:

report (web app)
– src
-mypackages
– context (web root)
-WEB-INF

share
– src
-mypackages
– persist

The XML is contained within “share/src/mypackage/persist” directory. All the other classes from the “share” project are included in the deployment, and the XML is included in the deployment IF the deployment is “exploded archive.” If I mark the deployment as “packaged” the XML files from the referenced required project are left out, though the web.xml from the WEB-INF is included. Strange.

Eclipse Version: 3.0.0, build 200406251208

[Kurtis Williams]

Hang on folks. I just figured out what my problem is. It turns out that it is including the XML files, just not where I thought. Is there a way to create a “packaged” deployment that does not jar up dependent projects? I’d like to just include the required projects in the source tree, not jar’ed up in the WEB-INF/lib.

[Riyad Kalla]

What happens when you change the deployment policy for “dependent projects” to “Smart” instead of “JAR and put in WEB-INF/lib”?

[Kurtis Williams]

The “Smart” deployment option jars up the dependent/referenced projects if the deployment is “packaged” and does not jar them if the deployment is “exploded.” I guess that’s what makes it smart! We need a third option – “packaged with merged dependent projects” or something.

To get around this, I just created a batch file to “jar up” the exploded deployment into a WAR file. Cumbersome and outside the scope of the IDE, but it works for now.

[Author]

Posts