-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
Scott Kuhn wrote:
Glad you got this working!
>
> I guess jserv loads non-servlet classes and keeps them loaded even if the servlet
>that loaded
> them is reloaded, which is probably good for efficiency.
>
This actually depends on where the non-servlet class was loaded from. If it was
loaded from the
system class path (i.e. one of the places you list in "wrapper.classpath"), then
auto-reloading
cannot occur, because such classes can't be reloaded. However, if you make sure that
your
non-servlet class is in a directory (or JAR file) listed in the "repositories" setting
of your
zone properties file, and NOT on the system class path, then changes to the
non-servlet class
file should trigger reloads just like changes to a servlet class.
Of course, you have to have the "autoreload.classes" property set to "true" to enable
reloading
at all. There is a modest performance hit for this check, so you would normally use
it only in
development, not in production.
>
> Scott
>
Craig McClanahan
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
