geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sachin Patel <>
Subject Re: Third party jars inside ear files
Date Sun, 10 Dec 2006 14:34:28 GMT
You should be able to package the jars directly inside the ear and  
the in the WAR's manifest add an entry to the jars in needs as a  
classpath entry.

On Dec 8, 2006, at 7:00 PM, David Jencks wrote:

> The only think I know of that you can do is to include a dummy ejb  
> jar file with no ejbs in it and put your libs in it's manifest  
> classpath.  It will need a skeleton ejb-jar.xml descriptor so it  
> can get deployed correctly.
> You are correct that the dependency elements only refer jars  
> outside the ear in the geronimo repository.  The other thing you  
> could do is to put the jars in the geronimo repo and use dependency  
> elements.  This is fairly easy if you use maven... .but still not  
> as easy as it should be.
> hope this helps
> david jencks
> On Dec 8, 2006, at 12:10 PM, Spotts, Joel ((ISS Atlanta)) wrote:
>> I have a number of third party jars I want to include inside an  
>> ear. I would like all my web applications to have access those  
>> jars. I realize that I can list those jars inside the manifest  
>> files of the wars (using the Class path directive), but that would  
>> mean that each war would load those jars in different class  
>> loaders. Is there a way I can designate that those jars I include  
>> in the ear should be available to the wars loaded by the class  
>> loader of the ear (such that the same class loader would load the  
>> jars for all wars inside that ear)? I have not found a way to  
>> configure that in the geronimo-application.xml. The closest  
>> directive I found is the dependency directive, but it seems like  
>> you can only load jars external to the ear (placed in the  
>> repository as separate compenents), but not for jars included in  
>> the ears?
>> Thanks,
>> Yoel Spotts


View raw message