Hi Joseph,
Joseph B. Ottinger wrote On 04/21/06 12:07,:
> Jan, incidentally, I tried the <application-library> tag as you
> suggested, and it did work properly.
Great! Actually, it was Jerome who suggested this.
Notice that if you place the JAR file(s) in the EAR file's default "lib"
directory, you don't need to specify any <application-library> in
your EAR file's deployment descriptor.
I'm not sure why the <application-library> approach would work, when
listing the JAR files in your WAR file's Class-Path manifest attribute
didn't.
In either case, the library JARs are loaded by the EJBClassLoader, which
is installed as the delegation parent of the WebappClassLoader of each
of the EAR file's packaged WAR files.
This means that even when you use the <application-library> approach,
the web container will still not be able to resolve any TLD resources
bundled in any of the library JAR files placed in <application-library>,
for the reason explained in
https://glassfish.dev.java.net/issues/show_bug.cgi?id=590.
I just verified this myself.
Is that what you are seeing?
Thanks,
Jan
>
> On Thu, 20 Apr 2006, Jan Luehe wrote:
>
>>
>>
>> Joseph B. Ottinger wrote On 04/20/06 15:55,:
>>
>>> My pleasure.
>>
>>
>> The issue is at
>>
>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=590
>>
>> Jan
>>
>>
>>>
>>> On Thu, 20 Apr 2006, Jan Luehe wrote:
>>>
>>>> Joseph,
>>>>
>>>> I'll go ahead and file the issue. Thanks for reporting it!
>>>>
>>>>
>>>> Jan
>>>>
>>>
>>> -----------------------------------------------------------------------
>>> Joseph B. Ottinger http://enigmastation.com
>>> Editor, http://www.TheServerSide.com joeo@enigmastation.com
>>
>>
>
> -----------------------------------------------------------------------
> Joseph B. Ottinger http://enigmastation.com
> Editor, http://www.TheServerSide.com joeo@enigmastation.com