Still, the main issue that remains is the jsp's. We have three options here:
- Creating symlinks: this solves the problem in linux. In windows we would have to copy manually or through a build script/maven extension the content from outside the project to inside the war. Always a risk to have different ways to build in different platforms. - Applying a patch: Applying the patch mentioned before to keep the same approach we use now with resin. This would be the least effort solution. But not the most reliable solution, as always have to mess with tomcat builds would be unacceptable. - Restructing the application: moving the related jsp's to inside the war is doable, but would take some effort. We would still have the shared jsps. They are managed by our content department using a CMS tool. They include headers, footers and some other common JSP's. They would have to be included in the war during packing or using symlinks in linux. regards Emerson On 21/02/2008, Ralph Goers <[EMAIL PROTECTED]> wrote: > We put a proxy in front of Tomcat. It serves all the static content. > > emerson cargnin wrote: > > 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. > > > > > > > > --------------------------------------------------------------------- > 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]
