RE: Esoteric class loading question/loading constraints/loader constraints

2004-03-24 Thread Caldarale, Charles R
From: Eric M. Kascic [mailto:[EMAIL PROTECTED] Subject: Esoteric class loading question/loading constraints/loader constraints Based upon my understanding of how the JVM tries to ensure type safety across ClassLoaders, StandardClassLoader loading the second version of class X should fail

RE: Esoteric class loading question/loading constraints/loader constraints

2004-03-24 Thread Shapira, Yoav
Hi, Your understanding is wrong: there can be one class X for each classloader. Your practice of using multiple classes with the same fully-qualified name in the same application is questionable, as it can easily lead to human errors. Yoav Shapira Millennium Research Informatics -Original

Re: Esoteric class loading question/loading constraints/loader constraints

2004-03-24 Thread Antonio Fiol BonnĂ­n
Hi Yoav, Of course you are right (you always are ;-) about the way classloaders work. However, I think Eric meant (and if he didn't, I do) that his class X is in fact a single one, and he *needed* to copy the .class file into common/... so that he could instantiate a new object of class X from