tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dies Koper <>
Subject Re: TCK Failed Was: Tomcat 5.5.18-beta preview
Date Tue, 29 Aug 2006 00:14:37 GMT
Hello Filip,

In my application I used a pageContext.include which once threw a 
JasperException (ServletException) while it was supposed to (according 
to the spec) propagate the IOException as-is.
I noticed that setting the "deployment" init param in conf\web.xml to 
"false" made it propagate the IOException correctly.

Apparently JspServletWrapper checks this flag and decides to handle 
exceptions differently depending on this value.
I did not look further into it as my problem is resolved, but I have 
been wondering why it would do this and whether to bring it up here.


Filip Hanik - Dev Lists wrote:
> Looks like the TCK is expecting a IOException, and not a runtime jasper 
> exception when you have invalid TLD files is one of the errors.
> -------------------------------------------
> Test FAILED.  Exception thrown by forwardedresource, but was not an 
> instance of IOException
> Type thrown: org.apache.jasper.JasperException
> -------------------------------------------
> ERROR: Exception at:
> ERROR: com.sun.ts.tests.common.webclient.TestFailureException: Test FAILED!
>    at 
> com.sun.ts.tests.common.webclient.WebTestCase.execute(
>    at 
> com.sun.ts.tests.common.webclient.BaseUrlClient.invoke( 
>    at 
> com.sun.ts.tests.jsp.api.javax_servlet.jsp.pagecontext.URLClient.pageContextForwardIOExceptionTest(

>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>    at 
> sun.reflect.NativeMethodAccessorImpl.invoke( 
>    at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(

>    at java.lang.reflect.Method.invoke(
>    at
>    at com.sun.ts.lib.harness.EETest.getPropsReady(
>    at
>    at 
> com.sun.ts.tests.jsp.api.javax_servlet.jsp.pagecontext.URLClient.main(

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message