----- Original Message -----
From: "Brian K. Buckley" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
> The Servlet API 2.3 specification disallows web applications from seeing
the
> server's internal implementation classes. The reason is to solve the
> problem which you've described.
<extracted from section 9.6.2 of spec ver 2.3 PFD>
The classloader that a container uses to load a servlet in a WAR must not
allow the WAR to
override JDK or Java Servlet API classes, and is recommended not to allow
Servlets in the
WAR visibility of the web containers implementation classes.
</extracted from section 9.6.2 of spec ver 2.3 PFD>
As you can see above, the spec *do not disallow* but *recommends* that the
implementation classes of the container should not be visible to the
servlets in the WAR.
This means that one can not depend that visibility of the web containers
implementation classes will be disallowed by the servlet container.
Another point which comes to mind is what comprises the server's internal
implementation classes? Does it also include some third party jar for xml
parsing etc?
Regds,
Gokul
>
> Brian
>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
