> -----Original Message-----
> From: Peter Donald [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 13, 2002 3:11 AM
> To: Avalon Developers List
> Subject: Re: ExclaliburComponentManager
>
> ....
>
> If the avalon jars are in the webapps lib dir (ie
> myapp/WEB-INF/lib/avalon-*.jar) then in theory you should be
> fine. Your
> servlet container *should* set the context classloader - if
> it doesn't then
> it is probably buggy.
>
So apparently Tomcat 3.2.3 does not do it. I'll follow Berin suggestions and will try
Thread.currentThread().setContextClassLoader(this.classloader);
in my FrontComponent servlet service method, so I can get rid of the hack.
> However if you keep your jars in other places (like in the
> servlet engines
> common directory or something) then I would expect to see the
> behaviour you
> describe.
>
> Could you describe where you are placing avalon jars and
> where the code that
> uses them is placed.
They are placed in my web app lib dir, not in tomcat lib dir.
Vincent
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
