aspose file tools*
The moose likes Websphere and the fly likes Mapping shared libraries at application level not application server level Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "Mapping shared libraries at application level not application server level" Watch "Mapping shared libraries at application level not application server level" New topic
Author

Mapping shared libraries at application level not application server level

Nicola Garofalo
Ranch Hand

Joined: Apr 10, 2010
Posts: 308
Hi,

i defined in the admin console a shared libray on my application server with name CommonLibs referring a directory containing some jar files.

I need to reference this shared library on my ear project without mapping the reference by administration console at ear deploy time

Is this possible writing something on some configuration file like application.xml or in Manifest.mf file?

I read the following article http://java.sun.com/j2ee/verified/packaging.html but i miss something,i mean, the Extension-list has to contain jar names or just CommonLibs, i.e. the shared library defined in my applicatin server?

Thanks for your help


Bye,
Nicola
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Mapping shared libraries at application level not application server level
 
Similar Threads
Regarding deployment on Websphere App server
migrating from Jboss4.0 to websphere 6.0
Passed 700,701 and 340 last Thursday
UnsatisfiedLink error
UnsatisfiedLink Error