Alex,
You could argue like that, but you could also choose to release
the jsp source directly to your production site. The penalty is then paid
by the first person that accesses that page. (because, if it is not
pre-compiled it gets compiled on the spot). You could also decide to
release the compiled versions, in which case nobody gets a penalty
for being the firts one to visit your site.
So you really you a couple of options here :-)
Actually releasing the compiled version gives you something
extra. It is harder to tamper with those, because you cannot
access the source code in the production environment. Which is
in a production environment probably what you want anyway ;-)
A development cycle would be to have a development
environment where you have the auto-compilation (that is you just
copy the jsp file). Once tested and rubberstamped, you release
the compiled jsp equivalents. The IT world has been following this procedure
for quite a few year now ;-), most satisfactory I might add.
Regards,
Cor.
-----Original Message-----
From: Alex Colic [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 25, 2001 21:04
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
