[EMAIL PROTECTED] wrote:
I am not expert. I use Tomcat and struts. I found that even though my appIn reality, the answer is generally simple. Your application (e.g. WAR file) should be a portable component. As such everything it needs that is not in the java.* and javax.* packages should be included in either the WAR file or as a utility jar in the EAR that contains the WAR. Even large components like GIS packages should follow this rule--most licenses allow it.
uses commons-dbcp, I don't have to include it into my WEB-INF/lib because it
is in Tomcat's common/lib. I guess the requirement is container based. Of
course, if "not to include" only works if all apps use the same release of
3rd party lib.
Otherwise it will become cost prohibitive to test every single application on the server whenever an update of one package comes out. If it is in the EAR or WAR you can test and deploy the apps one-at-a-time and depending on the budget priorities of the individual departments that own the apps. This will pay huge dividends as soon as one of your applications needs an overhaul sooner than another one, or more likely when one application goes untouched for 5 years and threatens to drag all of your new apps to its least common denominator.
This document explains most of the common scenarios. http://developer.java.sun.com/developer/technicalArticles/J2EE/build/
Regards, Evan.
--
Evan Schnell, Technical Lead
nVISIA, Twin Cities "Digital Architecture and Construction"
7701 France Ave. S, Edina, MN 55435
Voice: 952.837.2577 -- Fax: 952.837.2578 -- Mobile: 612.232.5972
smime.p7s
Description: S/MIME Cryptographic Signature
