Gudmundur Hafsteinsson wrote:
> > | You're right about the normal delegation model for Java2.
> > However, the Servlet
> > | 2.3 Spec (Proposed Final Draft) gives a servlet container
> > the option to "look
> > | before delegating" -- see Section 9.6.2. Tomcat 4.0 does this.
> >
> > I've been wo
> | You're right about the normal delegation model for Java2.
> However, the Servlet
> | 2.3 Spec (Proposed Final Draft) gives a servlet container
> the option to "look
> | before delegating" -- see Section 9.6.2. Tomcat 4.0 does this.
>
> I've been wondering quite some time: how can th
On Fri, 2 Feb 2001, Craig R. McClanahan wrote:
| > > -Original Message-
| > > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
| > >* Java asked the webapp class loader to find the
| > > controller servlet class
| > >* The webapp class loader did not find the class
| > > so it deleg
> WEB-INF/lib. In the 2.3 model, Y will override X. In the standard delegation
> model (i.e. Tomcat 3.2) you'd get the classes from X no matter what you did.
If you add a library to the CLASSPATH before starting tomcat 3.x - it'll
be used and no webapplication can override or change it.
But t
> The Java2 class loading model is for a loader to "delegate first" to it's
> parent loader. Only if the parent loader (that also delegates first to it's
> parent) can't find the class will the original loader try to load it.
>
The code in the main branch is doing exactly that - the class loade
Marc Saegesser wrote:
> > -Original Message-
> > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> >* Java asked the webapp class loader to find the
> > controller servlet class
> >* The webapp class loader did not find the class
> > so it delegated to the shared class loader
> >
> -Original Message-
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
>* Java asked the webapp class loader to find the
> controller servlet class
>* The webapp class loader did not find the class
> so it delegated to the shared class loader
>* The shared class loader (which reads
Arthur Ash wrote:
> Hi Folks,
>
> I'm having a general issue with the app-specific classpath (WEB-INF/classes
> and WEB-INF/lib/*.jar).
>
> Here is the scenario as I understand it:
> I have an MVC servlet/bean framework that is installed in the primordial
> classpath. It contains a single dispat
> I have another question, which has been nagging me for
> a while: Why does the class loader for a web-app "see"
> the classes in the lib folder of the servlet engine
> (or the classpath of the java engine).
The problem will be resolved in the main tree ( most of the
code is there, I think Nacho
I hope you don't mind me answering your e-mail
to the list, I think this deserves some discussion.
This is exactly what we've been doing, but it
requires fiddling with the libs of the servlet
engine, something I don't want to do!
I want to be able to separate the libs of the servlet
engine
> Am I just screwed or is there some cool trick that I am
> missing?
As far as I know, this is not possible.
I have another question, which has been nagging me for
a while: Why does the class loader for a web-app "see"
the classes in the lib folder of the servlet engine
(or the classpat
11 matches
Mail list logo