OK - good reasons. I'll buy that for a dollar, as you folks in the US like
saying. I guess I'll stick with developing things in servlet zones and
migrating stable classes to the server's classpath (whilst doing regression
testing to make sure the change to a shared semantics doesn't break
anything).
> -----Original Message-----
> From: Craig R. McClanahan [SMTP:[EMAIL PROTECTED]]
> Sent: 20 September 1999 17:24
> To: [EMAIL PROTECTED]
> Subject: Re: Memory allocation....I lost into that.....
>
> Even with auto-reloading turned off, each zone has its own class loader.
> Therefore, each zone will load its own copy of any required class that
> cannot
> be found on the system class path.
>
[Nick Rothwell] (As an aside, that must give "static" a curious
meaning, especially if servlet zone classes think they're capable of passing
unique generated timestamp values to centralised classes.)
___________________________________________________________________________
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
