Hi, Apologies if this is a duplicate post.. I searched the mail archives and the release notes before posting.. I am upgrading to Tomcat 4.1.12 + JBoss from Jboss/Jetty. I couldn't deploy my war directly, so its now wrapped inside an ear, with all the libs in a directory in the libs folder, and a manifest class-path entry to point to those libs. The application appears to function fine, except for this problem. I found a bug 10711 http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10711 that discusses the failure of jasper2 to properly compose a relative path with the jsp:include tag. I'm still seeing this on 4.1.12, even though it appears to have been fixed in 4.1.9 beta. Can someone please shed some light?
Here is the jsp:include information: <jsp:include page="../common/masthead.jsp" flush="true" /> Here is the manifest info in the war for this file and the included file: 8742 Tue Nov 12 10:11:48 CST 2002 tcm/tcm.jsp 377 Tue Nov 12 10:11:48 CST 2002 common/masthead.jsp Here is the version at the bottom of the 404 error page: Apache Tomcat/4.1.12-LE-jdk14 I'm running on Windows XP + JDK 1.3.0 + Jboss 3.0.4 + Tomcat version (above) Thanks, James
