OK, I know that there were some class loader subtleties, but hadn't
thought it through that far. What you're saying is that: if *any* reload is
forced (i.e. even one .class file for a servlet is changed) the class loader
is discarded, so that all servlets in that zone are also lost. It makes the
semantics curious, but seems relatively simple and consistent.
It sounds as if mixing servlet-loaded stuff and system-loaded stuff
is A Bad Thing. For development, I put all of my stuff into a servlet zone
(so that it's all loaded by the same class loader), but the standard
classes, JSDK, JDBC and so on are on the system side, so any links from
there into servletland would be potential trouble.
[Nick Rothwell] > By the way, I would not recommend running a
production application on Apache
> JServ with auto-reloading enabled. Besides the potential for class cast
> errors, there is a small performance penalty.
>
[Nick Rothwell] Noted, and for deployment we'll be turning all the
clever stuff off.
(Sorry about the email formatting - again. I *detest* Outlook.)
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
