I'm still running the tests, I had some funky results come up when I
turned off development, and I am re-running the tests to make sure it
wasn't me screwing it up
Filip
Remy Maucherat wrote:
Dies Koper wrote:
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.
It's "development". Indeed, it seems to be the reason: the original
exception gets wrapped for nicer error reporting purposes. If
development mode is off, then the original exception will be passed,
so the test should then work.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
