This content has been marked as final. Show 4 replies
JSP compilation is not controlled by JBoss. JBoss only deploys files to the respective service, in this case either Tomcat or Jetty depending on your distribution bundle. Both servlet containers use Jasper. By default Jasper should only compile when the JSP changes (time stamp), or if it is packaged in a WAR file, when that WAR file time stamp changes. However, if you don't like the settings, you can modify them. The following example gives a production type setting - read the Jasper howto for greater detail.
If Jetty, check server/instance/deploy/jbossweb-jetty.sar/webdefault.xml. There will be a Jasper configuration setting. Try configuring it like this:
This will also work for Tomcat. Check server/instance/deploy/jbossweb-tomcat.sar/web.xml.
This applies for JBoss-3.2.x. Read the additional information on Jasper in these configuration files. You can also check the Tomcat website for more on Jasper 2 configuration. http://jakarta.apache.org/tomcat
We've had this problem before with a new server - the JSPs kept being re-compiled.
The problem was that the server was setup with its system clock in a different timezone to the development PC. Tomcat kept thinking that the file had been updated because the date/time of the war file was older than the jsp files contained within it. Deploying the war file to the server was adjusting its file timestamp between the different time zones.
yeah yeah yeah, it works ... the problem was the time difference between deploy and develop ...
thx for your answers ...
Worked for me too THANX!!!
The time on the dev machine has to be behind the servers