Well, I said at the beginning that I'm not a big fan of this approach, but I understand the reasons behind it and the difficulties it would have to change it.
Other reason for using this approach is when you have a great amount of static content, like images. An update of the war would have to include 1 or more giga of images and static html pages. What about if you have different applications (wars) that share common headers, footers, images, etc? Now people usually do it using symlinks, which makes it difficult using windows. regards emerson On 19/02/2008, Caldarale, Charles R <[EMAIL PROTECTED]> wrote: > > From: emerson cargnin [mailto:[EMAIL PROTECTED] > > Subject: Re: Mapping JSP's to outside of the war or expanded folder > > > > and... any idea on how to map to the jsp's outside? > > Nobody ever need it? how do people migrate from resin then? > > Nobody needs it because it's a clear violation of the servlet & JSP > specs. It's somewhat ironic that your company appears to have a policy > that requires non-adherence to the technology specification they choose > to employ. The fact that resin supports such a violation is just > another example of how some vendors try to lock customers into their > unique implementations by providing non-compliant capabilities. > > - 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] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
