[2220] in java-interest
Re: Heres a confusing thing...
daemon@ATHENA.MIT.EDU (Jonathan Payne)
Wed Sep 27 04:25:06 1995
Date: Tue, 26 Sep 1995 13:18:20 -0700
From: jpayne@starwave.com (Jonathan Payne)
To: chanda@PRPA.Philips.COM
Cc: java-interest@java.sun.com
In-Reply-To: <9509261811.AA15336@annex.PRPA.Philips.COM> (chanda@PRPA.Philips.COM)
They're not the same answer, but you'd have to know about the yucky
internals to understand the answer.
Ignore 2. It's too hairy to contemplate.
> Date: Tue, 26 Sep 95 11:11:57 PDT
> From: chanda@PRPA.Philips.COM (Chanda Dharap)
> Sender: owner-java-interest@java.sun.com
> Precedence: bulk
> X-Info: To unsubscribe, send 'unsubscribe' to java-interest-request@java.sun.com
> Content-Type: text
> Content-Length: 1600
>
>
> Someone posted the following question and now there are two distinct
> replies.
>
> Which one guys ??
>
> - Chanda Dharap
> ------------------
> email: chanda@prpa.philips.com
>
> --------------------------------------------------------------------
> Can I define my own class loader which loads classes from the file
> system? If I do, will I be subject to the security measures which are
> in place for WWWClassLoader, which loads classes from the network? Or
> are the security measures dependent on that particular class loader
> subclass?
>
> Also, if my class loader periodically checks the file system for an
> update to that class, and reloads that class, will the system actually
> successfully start using the new definition of the class. Something
> tells me that it will actually continue to use the original
> definition, because the class is actually stored internally in the
> interpreter.
> -----------------------------------------------------------------------
> 1>The next time that the class is loaded from that class loader it will
> 1>return the new class. The old class will eventually be gc'd (although
> 1>that isn't implemented). Existing instances of the new class will not
> 1>automatically be upgraded.
>
> 2>Your latter statement is the more correct one. It is of course possible
> 2>to define a native method in your class loader that does a manual substitution
> 2>on the internal class list however that is probably a fairly dangerous
> 2>operation, especially if you make an incompatible class change.
>
> -
> Note to Sun employees: this is an EXTERNAL mailing list!
> Info: send 'help' to java-interest-request@java.sun.com
>
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
