tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Goldstein" <Scott.Goldst...@bluejungle.com>
Subject RE: Precompile jsps into work directory
Date Sat, 01 Oct 2005 00:05:28 GMT
Never mind.  I searched the list again and found the answer.  Though I
haven't tried it, yet, it looks like with the proper arguments (output
directory, package name, etc.) to JSPC, you can manipulate it to compile
the jsps to the work directory and not have to insert the servlet
definition fragments in web.xml.

 

This seems like a task which should be automated through an option in
the JSPC task.  Why?  Suppose that I have a WAR file which I would like
to deploy on multiple application servers.  Each app server may have its
own jsp compiler.  I don't see why I should have to build separate WAR
files in order to precompile jsps for each application server.  Ideally,
I could build one WAR file and then precompile for each application
server.  

 

Scott

 

________________________________

From: Scott Goldstein 
Sent: Thursday, September 29, 2005 8:47 PM
To: 'tomcat-user@jakarta.apache.org'
Subject: Precompile jsps into work directory

 

I've searched the archives and couldn't find an answer to this question.
The Tomcat manual suggests using Jspc to precompile jsps.  The method it
describes precompiles the jsps and creates stub servlet definitions for
each jsp to place within web.xml.  Instead of this method, I would like
to simply precompile the jsps into the tomcat work directory.  I know I
can do this by requesting each jsp with the precompile request
parameter, but I'd like a command line/Ant method of doing this without
having to run the server.  

 

Has anyone tried/been successful in doing this?

 

Thanks.

 

Scott


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message