Peter Donald wrote:
> On Wed, 13 Feb 2002 10:02, Vincent Tencé wrote:
>
>>I wanted to know I you have also experienced that problem when using Avalon
>>with servlet containers.
>>Is it a tomcat issue? I am not very familiar with class loader issues. Is
>>there a better way
>>to get the same result than the hack code above? What is the preferred way
>>of doing things here?
>>
>
> 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.
>
> 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.
>
>
>
>>Btw, I guess there is mistake in the paper Developping with Apache Avalon
>>at bottom of page 39 (pdf format).
>>There is an example of an xml configuration file and it says that when you
>>have multiple instances
>>of a component you specify the instance name with the "hint" keyword but
>>the code is expecting "name" instead.
>>
>
> Berin - do you wanna pick this up.
I'll apply the patch.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
