> > Actually, the JVM spec (1.2.2 & 1.3) forbids having two different
copies of
> > the same class under the same JVM, even if the copies were loaded using
> > different class loaders (section 5.3.4, "Loading Constraints").
> Not exactly. It's more along the lines that related
> classloaders can't contradict one another. But it's
> certainly possible for two different classloaders to
> load a class with the same name. Otherwise webapps in
> servlet containers wouldn't work...
What do you mean by "related class loaders"? I couldn't find it in the
spec...
The JVM has one classloader of its own (the bootstrap classloader). Consider
it
has two different web applications inside, hence - two classloaders,
"brothers"-like
related. Is contradiction allowed here?
- Isaac
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
