> Some time ago I was discussion the new JBoss
> features and I told him about the new dynamic
> classloader in JBoss. He then asked me what
> happens with Class-variables when we drop
> the old class and load the new class.
This also happened since the beginning of the days when garbage collector
thinks that a class is not useful and disposes its memory. IIRC it was a big
*warning* sign on the Java forums (singleton pattern topics) on the 1.2
times.
If my java class is unloaded I expect all his static fields to be
initialized again. To try to think about it for me and make weird things in
its place should not be a good idea IMHO.
My code has places where you can find those nasty
public MyClass
{
private static Field myField;
static
{
myField = // static initialization here
}
}
This case should have to be supported - mucho pain and no gain. Honestly I
think that losing the static variables is OK.
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
