----- Original Message ----- From: "Kevin A. Burton" <[EMAIL PROTECTED]> To: "Ant Developers List" <[EMAIL PROTECTED]> Sent: Monday, February 04, 2002 12:54 Subject: Re: [PROPOSAL] 'redefine' task that uses JDK 1.4/JPDA class redefinition
> If a redefined class has instances then all those instances will have the fields > defined by the redefined class at the completion of the call. Preexisting fields > will retain their previous values. Any new fields will have their default > values; no instance initializers or constructors are run. ooh. actually this makes sense from a debug perspective, which is what JPDA is meant to be about; the implementation of edit-and-continue > The canUnrestrictedlyRedefineClasses functionality is what is needed but JDK > 1.4 doesn't support this. Of course there is also NO documentation about when > this will happen. > > God I hate closed source :( in a couple of places in the java bugbase there are comments of mine to that effect, roughly going "if you dont know what you are doing, leave the code alone, and if you arent going to fix what you have done, give us the source and let us do it ourselves". related to incompatible behaviour changes between 1.2 and 1.3... > Tomcat can't do dynamic reloading. It can't reload a single class. It has to > reload whole web contexts. It may seem that you are just reloading one class > but really the ClassLoader just obsoleted itself and the new classloader > redefines clases. ok, maybe it was bluestone then, I forget. All I know is now my code to retrieve a servlet context validates what we got back rather than just assumes that it is ok, even though being an immutable object its state should always be valid. -steve -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
