get the compile error on the live site.
That can't happen with precompliation.
> -Ursprüngliche Nachricht-
> Von: Charl Gerber [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 17. Juni 2005 10:28
> An: Tomcat Users List
> Betreff: Re: AW: JSP pre-compile and Apache
>
&g
ailto:[EMAIL PROTECTED]
> > Gesendet: Freitag, 17. Juni 2005 08:07
> > An: Tomcat Users List
> > Betreff: Re: JSP pre-compile and Apache
> >
> >
> > I have the precompiled JSP's working with Apache
> now.
> > Thanks.
> >
> > Apa
[EMAIL PROTECTED]
> Gesendet: Freitag, 17. Juni 2005 08:07
> An: Tomcat Users List
> Betreff: Re: JSP pre-compile and Apache
>
>
> I have the precompiled JSP's working with Apache now.
> Thanks.
>
> Apart from the "first-time-hit" compilation penalty on
>
I have the precompiled JSP's working with Apache now.
Thanks.
Apart from the "first-time-hit" compilation penalty on
a normal jsp (as apposed to a precompiled one), why
would you choose one option above the other?
Standard jsp is easier to do updates if you work in an
unpacked war setup - you jus
Have you granted the site accessClassInPackage runtime permission?
-Terence M. Bandoian
[EMAIL PROTECTED]
> I used to precompile my JSP's (which worked great and
> was a big time saver in testing), but since running
> Tomcat 4.1.31 together with Apache, all sorts of weird
> errors occurred. I re
OK, so it migth be well worth my while to look into
the issue again and see if I can get the precompiled
JSP's running with Apache.
(I originally did this a year ago).
Charl
--- Tim Funk <[EMAIL PROTECTED]> wrote:
> Apache doesn't care about the existence of a jsp.
> There is one exception -
Apache doesn't care about the existence of a jsp. There is one exception -
default pages when / (or /stuff/) is requested. In that case - apache will
look for index.jsp (Assuming that is a default page to be served) and then on
seeing the existence of that file - pass the request onto tomcat.
I used to precompile my JSP's (which worked great and
was a big time saver in testing), but since running
Tomcat 4.1.31 together with Apache, all sorts of weird
errors occurred. I remember reading somewhere that
Apache expected the actual jsp file, not the compiled
version. So I reverted back to *n
