Hi,

Mhhh, my experience with that "precompile issue" (and meanwhile I have a lot
of it :) says that it is not a problem of servlet loading order at startup,
but you can't access *any* jsp until the server is *completely* up!
Completely up means *all* servlets that must be loaded upon startup have to
be done with their init-method. And thus you can't write a servlet that
accesses a jsp in it's init-method and you can't forward to a jsp... That's
why we need that "magic hook" we are asking for for some days now. As soon
as I am through with all my current weirdness at work I will scan for that
hook myself...

If any developer can say that I am totally wrong -> please do so! And if
someone could point me to the right piece of source -> please do so!

Another thing I keep asking myself (especially after reading the "This would
be cool in tomcat as well" thread) is how to add non-portable features to
tomcat, so that it still is a clean reference implementation, but has
additional features that clearly do not belong to the servlet-spec...

pero

> -----Original Message-----
> From: Ralph Einfeldt [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 19, 2001 4:59 PM
> To: Tomcat Users List
> Subject: AW: Precompile JSP
>
>
> Just another version of 'How to shoot your self in the foot':
>
> - Make a servlet that loads on startup.
> - From this servlet make a forward to a jsp
>   that does what ever you want after the
>   JSP servlet is started.
>
>   Through the forward you force the startup of the JSP
>   servlet. In the jsp you can asume safely, that the
>   JSP servlet is already running. (8}
>
> > -----Urspr�ngliche Nachricht-----
> > Von: Nikola Milutinovic [mailto:[EMAIL PROTECTED]]
> > Gesendet: Montag, 19. November 2001 14:54
> > An: Tomcat Users List
> > Betreff: Re: Precompile JSP
> >
> >
> > > Precompile all the jsp files in your project in your
> > ant.xml file as
> > > part of the build process when making your war file.
> >
> > Yes, yes, it can be done, but what we want is to have JSP
> > normal and then precompiled upon context mounting. Startup
> > servlet cannot do it, since it starts before JSP servlet. Can
> > that be re-ordered somehow? To have something run UPON
> > startup, but AFTER JSP servlet?
> >
> > Nix.
> >
>
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>
>
>


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Reply via email to