> What I would like to know is this: how difficult
> would it be to reload the
> definition of a class if objects of the class had
> already been
> instantiated, then destroyed and garbage-collected?
> java.lang.ClassLoader caches Class objects so that
> class files don't have
> to be loaded or resolved more than once. While it
> would be easy enough to
> tweak ClassLoader to not do this caching, or to do
> it more controllably, I
> have a feeling the JVM might not like that very
> much.
Actually, creating your own class loader would be the
best way I know of. The VM spec allows you to make
your own class loaders to allow for obscure ideas like
this. I'd like to see someone do that in C++ and keep
all their hair.
Ken
_________________________________________________________
Do You Yahoo!?
Free instant messaging and more at http://messenger.yahoo.com
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
