You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/02/03 14:44:21 UTC
DO NOT REPLY [Bug 16701] New: -
No exception if jsp:include fails
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16701>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16701
No exception if jsp:include fails
Summary: No exception if jsp:include fails
Product: Tomcat 4
Version: 4.1.12
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Normal
Priority: Other
Component: Jasper
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: g.sauer-limbach@vcontarget.de
If the standard action jsp:include fails to locate the resource
(say JSP file) specified in the page attribute, there is no
exception generated. Tomcat does just do nothing about the
failed include action, but leaves the place in the response
empty.
Tomcat 3.2 did throw a java.io.FileNotFoundException, which I
would also expect to obtaine using Tomcat 4.1.
I did not try other versions of Tomcat 4, but two different
installations of Tomcat, one 4.1.12, antoher 4.1.x had the
same problem.
I checked not to be confused by the ErrorPage (removing the
part in the page directive), also put try/catch around the
include with various exception classes; none showed any
evidence of an exception thrown by the code executing the
jsp:include action. Using pageContext.include() behaves the
same.
jsp:includes does work well if the page can be found.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org