Henning,
An ounce of empiricism would do wonders ;-)
Simple rule: your servlets should be located in your servlet zone. Each time
a servlet is called (referenced, asked for ?) the servlet classloader
checks the .class file to see if it has changed. If it has it is reloaded.
Classes accessible
jon * wrote:
> > That means a servlet com.foo.bar.Servlet instantiating com.foo.bar.HelperClass
> may
> > not lie in in the same directory structure "com/foo/bar"?
>
> No. You can do that. What it means is what you said..the servlets must not
> be reachable by the classpath that is defined in wra
> You mean the servlets itself must not be reachable by the classpath assembled
by
> "wrapper.classpath" in jserv.properties but only by the zones repository
statement?
Yes. The issue is that the system classloader cannot be re-instantiated.
Only user defined classloaders (ie: jserv's classloader
jon * wrote:
> You need to take your servlets out of your system classpath.
>
> -jon
You mean the servlets itself must not be reachable by the classpath assembled by
"wrapper.classpath" in jserv.properties but only by the zones repository statement?
That means a servlet com.foo.bar.Servlet insta
> We're using Apache1.3.4 and JServ1.03b on Solaris 2.6. We're wondering how to
> tell JServ to reload modified servlets/classes without restarting Apache.
We've
> got "autoreload.classes=true" in our servlets zone properties but that doesn't
> seem to do the trick.
You need to take your servlets
