When we distribute our application to clients (initial and updates)
we distribute a .WAR file. That .WAR contains the entire webapp.
Yes, changing one JSP would cause you to have to run JSPC and javac
before distribution, but that process would take place on your build server
or workstation, not the system that is probably in production and using its
CPU cycles for real users. However, the translation and compilation process
is why we don't use JSPC on the development machines -- it does cause more
headaches during active development.
Also, Ant is really useful during this process - it does a checkout,
JSPC, compile, WAR, and FTP of the binary (only to test server, though - we
don't want to send updates out without testing them).
Randy
> -----Original Message-----
> From: Alex Colic [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 25, 2001 3:04 PM
> To: Tomcat-User
> Subject: RE: Why won't tomcat run with jre
>
>
> Hi,
>
> what I mean is that servlets will work but JSP's will not. As
> for the JSPC I
> did not think about that but..lets say you want to make
> changes to the jsp
> page. Do you have to make the change, recompile the page and
> then replace
> it? If so does that not make it more difficult to manage the pages?
>
> Alex
>
> ************
> What do you mean by failing? Tomcat only needs the JDK if you are
> using JSPs. What we do is use JSPs in development and then
> use JSPC to
> convert the JSPs to servlets for testing and production.
>
> Randy
>
