> > 2. Run a startup servlet, which will precompile all JSPs in your
> > webapp (request them with URL "/path/file.jsp?precompile=true", I think)
>
> As I wrote before this is not possible, because a jsp can first be accessed
> after the container is *completely* up - including all servlet-startups! And
> so the servlet tries to precompile the jsp forever... I learned that the
> hard way :-) So you would need another way to hook your precompiler into the
> container...
(sigh) and I thought it was such a good idea...
Could we have a startup servlet that would wait for a JSP servlet to start-up and then
call all the pre-compilations? Or just wait for a while? (That sucks as an idea, I
know)
We definitely need a regular "hook" for this.
Nix.
