> From: emerson cargnin [mailto:[EMAIL PROTECTED] > Subject: Re: Mapping JSP's to outside of the war or expanded folder > > Other reason for using this approach is when you have a great amount > of static content, like images.
One would normally package a large amount of static information in a separate webapp, so it would not have to be reloaded when something in the dynamic ones change. > What about if you have different applications (wars) that share common > headers, footers, images, etc? That should be handled during creation of the .war, not via deployment tricks. Whatever scripts you use to build the war files should copy the common stuff from one location into each war. Again looking at the servlet spec, the philosophy is to keep webapps as independent as possible. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
