I ran into this same problem, what I ended up doing is writing a little
utility which is auto-started by Orion. It just goes out and makes a
connection to the servlet forcing the initialization at start up.
-jason
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Daniel Lopez
> Sent: Friday, March 30, 2001 4:29 AM
> To: Orion-Interest
> Subject: Re: SV: load-on-startup is not working
>
>
> Hi Patrick,
>
> My problem is not that my servlet doesn't work. The servlet works but it
> is initialised when I perform the first request. It has to open database
> connections, parse a couple of xml files... at init time so I'd like to
> have it pre-loaded so the first request doesn't take too long. Orion
> doesn't have to compile my servlet as the servlet is already compiled
> and packed in a war file.
> Thanks anyway,
> Dan
>
> > Patrik Andersson wrote:
> >
> > Check your error log for compile time errors. is development="true" in
> > orion-web.xml so that Orion even tries to compile the servlet?
> >
> > regards,
> > Patrik Andersson
> >
> > -----Ursprungligt meddelande-----
> > Från: Daniel Lopez [mailto:[EMAIL PROTECTED]]
> > Skickat: den 30 mars 2001 10:54
> > Till: Orion-Interest
> > Ämne: load-on-startup is not working
> >
> > Hi,
> >
> > I don't seem to find how to get the load-on-startup attribute to work.
> >
> > This is the web.xml snippet where I use it:
> > ...
> > <servlet>
> > <servlet-name>GuiaController</servlet-name>
> > <servlet-class>org.leaf.LEAFManager</servlet-class>
> > <load-on-startup>1</load-on-startup>
> > </servlet>
> > ...
> > I've also tried with <load-on-startup/>, but to no avail. This has
> > been
> > working for me with Resin and other containers but it doesn't work
> > with
> > Orion.
> > What I am doing wrong?
> > Notes:
> > .- I'm pretty sure web.xml os being read as the application works fine
> >
> > after the first request, and if I add a typo to the web.xml file, I
> > get
> > an error message. The strange thing is that I don't get the error
> > message through the logs or the standard output, but when I try to
> > access for the first time.
> > Any hints?
> > TIA,
> > Dan
