I'm guessing you are referring to the css as a relative path -- ie
path/to/css.
If the CSS file is referred to as
${pageContext.request.contextPath}/webappRel/path/to/css, it will always
be found regardless of webapp context or servlet path. The browser
doesn't have to guess anymore. The same goes
I've encountered similar problems with a session variable hitting a servlet
then calling a JSP page.
I accounted for it by making two CSS paths -- one for the regular, initial JSP
and then a second for the calling JSP from the servlet.
Not what I wanted to do, but it did work ok.
-Original
