I'm glad that you have a solution and I too agree that it is better to keep the .css extension on a css file, since other components may depend on it.
But I just wanted to let you know that if you decide to refactor the project at a later date, and if you move the css file up or down at least one directory level than it is currently at, then all the relative paths inside the css file would have to be revised to the new relative path. There would be no need to revise the paths if a (root) context relative path was used. It's just a trade-off -- one way or the other it is possible to make things work (as already suggested by many different solutions on this thread). Also, projects typically have one main css file throughout , so having relative paths inside the css file should not be an issue, since it means changing only one css file. -Cheers Rashmi On 3/28/07, Mike Quilleash <[EMAIL PROTECTED]> wrote:
Thanks for all the replies. I will stick with the relative paths for now as that seems simplest. I also agree about keeping the css files "clean". I would prefer not to use the JSP workaround for inserting the context path. I will look into the virtual hosts tho to see if it might be useful in the future. Thanks again, Mike.
--------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
