Revisit Slow JBOSS EAR Deployment

[jcorbin4607]

I am using JBOSS 3.2.1 with Tomcat.

Yes, I have queried the history for information on this and have found a great deal that has helped, but wanted some definitive answers from the community.

There has been lots of discussion about why JBOSS 3.2.x recompiles the JSP's from a WAR file everytime the application is hot deployed or initially started. I want to make sure my understanding is correct and how I can alleviate the redeployment recompilation of all JSP's everytime.

Has there been any definitive solution that isn't a hack for this problem?

I have set the DeleteWorkingDir attribute to false and this doesn't work and I think people have found that JBOSS is deleting the tmp deployment directory each time and that is why recompilation happens.

I thought there was another attribute that could be set to specifiy another directory location for the exploded WAR. If there is, what is it?

Lastly, is the way to correct the recompiliation problem with JSP's every time an application is hot deployed to set the
DeleteWorkingDir to false
and specify a alterative directory location for the exploded war file?

TIA,
J.D.

[jonlee]

Currently, under Tomcat under JBoss does not provide a way in which to prevent deletion/cleanup of the temporary files created, including the .java and .class files derived from the JSP. I do not believe the DeleteWorkingDir is processed in any meaningful way.

You can enable debug for server.log and observe the output to see whether it processes the tag. You will probably find it has no discernible or recognised action for the tag.

There has been a method suggested in the forum to configure Jasper to generate the temporary files in a separate directory. It is a bit messy.

Jetty has a configuration setting that allows a temporary directory to be specified on a per WAR basis. It is also described in the forum.