It's a good point, thanks. I guess this behavior is standard for contexts not reloadable automatically. Paul
On Sunday 01 December 2002 01:28 pm, Reynir H�bner wrote: > I've have got this error, when a class that the servlet uses has changed. > > If a class that the servlet relies on has been changed and compiled > afterwards the servlet was compiled it may report as unavailable. Because > this is an error you should get at compile time, but not runtime. > > There may be other reasons, such as reliant class missing in classpath etc. > > Hope it helps > -reynir > > > -----Original Message----- > > From: Paul Yunusov [mailto:[EMAIL PROTECTED]] > > Sent: 1. desember 2002 15:02 > > To: [EMAIL PROTECTED] > > Subject: "Servlet unavailable" discussion > > > > > > Hello, > > > > I was wondering what, in general, can cause a servlet to be > > "unavailable" as > > reported by a StandardWrapperValve of Tomcat 4.1.12. > > Thanks, > > Paul > > > > -- > > To unsubscribe, e-mail: > > <mailto:tomcat-user-> [EMAIL PROTECTED]> > > For > > additional commands, > > e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
