It is recommended to keep the stuff local to avoid "jar hell."
-----Original Message-----
From: twcrone@xxxxxxxxxxxxx [mailto:twcrone@xxxxxxxxxxxxx]
Sent: Wednesday, February 15, 2006 11:02 AM
To: users@xxxxxxxxxx
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
|