Why does it all need to be the same physical file? I would use the css import statement to import your global.css as shown below and then link the global.css file to your pages (as you mentioned)...this will give you ability to seperate your css but avoid the bother with the jsp includes.
@import url(../global/i_base.css); @import url(../global/i_header.css); @import url(../global/i_footer.css); @import url(../global/i_layout.css); @import url(../global/i_button.css); On Fri, Oct 23, 2009 at 10:09 AM, rowlando <n...@rowlando.com> wrote: > > > Pid Ster wrote: >> >> On 23/10/2009 11:50, rowlando wrote: >> >> Why? >> >> - Why do this with a JSP/Servlet? >> >> - Why not concatenate it into a single CSS file at build time, prior to >> deployment? >> >> - Why not use the CSS import directive? >> >> Serving it via a servlet risks preventing the browser from caching it as >> effectively. >> >> > > I am building a static site. I'm using JSPs purely for Includes. The build > process is a simple web crawl, where every HTML page is saved as a file. > -- > View this message in context: > http://www.nabble.com/How-to-use-Includes-in-CSS-files-tp26024235p26028142.html > Sent from the Tomcat - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > -- Curtis Garman Web Programmer Heartland Community College --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
