If I anticipate a versioning issue for a jar across apps, I will put the files
within my EAR. In the case of WLS 8.x, for example, under APP-INF/lib where
they'll automatically be included in the app-level classloader. In earlier
versions, I'd manually create a lib dir under the root of my EAR, and
reference these via manifest classpath entries.
I'm not a fan of huge system classpaths, so don't tend to use that for much
beyond the server itself, DB drivers, and any "oddball" jars that must precede
the appserver jars due to versioning issues (e.g. saaj.jar before
weblogic-webservices.jar).
Some appservers, such as BES, offer some folders for deploying jars that are
shared across apps in a managed instance, but which are a step down from the
system classpath level.
Patrick W. McMichael
---------- Original Message -----------
From: twcrone@xxxxxxxxxxxxx
To: users@xxxxxxxxxx
Sent: Wed, 15 Feb 2006 16:01:49 +0000
Subject: [cinjug-users] Common jar files on app server
> In the past I've simply included jar files in the ear file that they
> are being used rather than try to deploy them to the server itself
> and have them used by other apps. This way I can deploy apps that
> use newer versions of things like Hibernate, Spring and Log4J
> without affecting other apps that might use older versions.
>
> Does anyone know what the best practice is for the placement of jar files
>
> (server or project) that tend to be common throughout several
> applications but could have newer versions for newer applications?
>
> Where does everyone typically put their Spring and Hibernate jar
> files on their respective app server? We are using WebSphere V6.
>
> --
> twcrone@xxxxxxxxxxxxx
> 859-278-9634
>
> ---------
> You may unsubscribe from this mailing list
> by sending a blank email addressed to:
> users-unsubscribe@xxxxxxxxxx
>
> --
> Find additional help by sending a blank email
> addressed to:
> users-help@xxxxxxxxxx
------- End of Original Message -------
|