Scott M Stark wrote:
> You showed the web.xml descriptor and I expected that this did declare
> the servlet in myLib.jar or there would be no reason for the
> servlet to
> be deployed. I'm saying that I don't think this is valid
> behavior as you
> could not just extract the war and deploy it. My reading of the specs
> says that the war is not valid and should not deploy.
The Servlet spec requires that the class is in the class path.
Accordingly, in the META-INF/manifest.mf file for myWeb.war, there is an
entry that reads thusly:
Class-Path: myLib.jar
The reason this is built like this is that the servlet is a generic piece of
infrastructure which uses locally provided classes (instantiated by
reflection) to implement a Model2 architecture. As we expect to deploy
several web apps (each in their own WAR) in the final EAR, we have the
servlet in an external library JAR. All perfectly legal according to the
J2EE spec.
Sorry if that wasn't clear before. :) Anyway, to get back to the core of the
problem:
Is there an object that the servlet has access to (such as the ServletConfig
or the ServletContext) that is certain to be instantiated by the classloader
for the Web App? If I can get such an object, I can use its classloader to
instantiate the other classes.
Robert.
--
"Duct tape is like the Force: it has a light side, a dark side,
and it holds the universe together"
Robert Watkins [EMAIL PROTECTED] [EMAIL PROTECTED]
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
