I am a Tomcat newbie.   We use Tomcat 5.5.23, *Nix and Windows.
My recent experience was that in my development environment, if I had
the application web.xml
(as opposed to global web.xml under conf directory)
with the mappings as specified below, then Tomcat refused to compile and
was looking for
precompiled classes.
Then, I removed the mappings from the application web.xml, put ant.jar
and tools.jar in
$Catalina_HOME/commmon/lib and removed jasper-compiler-jdt.jar from the
same place for 
Tomcat to compile the JSP files on the fly.

In the production environment, with the web.xml as defined below, and
with precompiled classes
placed in the proper location, Tomcat does not try to compile at all, as
desired.

So in summary, I did not do anything special to "disable" compilation
but rather I had to do
the steps outlined above to "enable" compilation.

--Lakshmi

-----Original Message-----
From: lightbulb432 [mailto:[EMAIL PROTECTED] 
Sent: Friday, May 25, 2007 12:32 PM
To: users@tomcat.apache.org
Subject: RE: Excluding JSP compiler from Tomcat


In your production environment have you "disabled" or "excluded" the
actual Tomcat piece that does the JSP compilation, to decrease the size
and memory usage (no matter how small) of the production Tomcat install?
The part of the JSP spec that I referred to in my original post seemed
to indicate that it might be possible depending on your container. As
Tomcat is the RI, I'm wondering whether this capability is available.



Lakshmi Venkataraman wrote:
> 
> In our development environment we compile JSPs on the fly.
> In our production environment we have precompiled JSP classes.
> 
> In the PRODUCTION environment, webapps/WEB-INF/web.xml have <servlet> 
> and <servlet-mapping> defined for every JSP page.
> For example:
>   <servlet>
>        <servlet-name>MyAppJsp1</servlet-name>
>        <servlet-class>jsp.myAppJsp1</servlet-class>
>     </servlet>
>     <servlet-mapping>
>         <servlet-name>MyAppJsp1</servlet-name>
>         <url-pattern>/jsp/MyAppJsp1.jsp</url-pattern>
>     </servlet-mapping>
> 
> The precompiled JSP classes are placed inside WEB-INF/classes/jsp. I 
> guess you can also probably archive these files in a WAR file.
> 
> 
> --Lakshmi
> 
> -----Original Message-----
> From: lightbulb432 [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 25, 2007 10:31 AM
> To: users@tomcat.apache.org
> Subject: Excluding JSP compiler from Tomcat
> 
> 
> The JSP spec says that if you precompile JSPs you can reduce the JSP 
> container footprint by excluding the JSP compiler. How can this be 
> done in Tomcat?
> 
> Thanks.
> --
> View this message in context:
> http://www.nabble.com/Excluding-JSP-compiler-from-Tomcat-tf3817429.htm
> l#
> a10807251
> Sent from the Tomcat - User mailing list archive at Nabble.com.
> 
> 
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, 
> e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, 
> e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

--
View this message in context:
http://www.nabble.com/Excluding-JSP-compiler-from-Tomcat-tf3817429.html#
a10809085
Sent from the Tomcat - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to