Nick Rothwell wrote:
> 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.
>
That's pretty much what happens. But keep in mind that we are talking
specifically about Apache JServ -- other servlet engines may do things
differently.
>
> 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.
>
I use pretty much the same organization -- JDK system classes, JDBC drivers,
and all that kind of stuff are put on the system class path (with the
wrapper.classpath setting), and all my classes are in zone repositories. I
also double check to ensure that no directories or JAR files are on both
lists. If they are, the current Apache JServ class loader considers them
system classes, and that can lead to even more confusion trying to figure out
what is going on..
Craig
___________________________________________________________________________
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
