-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error page tests #14
Comments
we unwrapped the exception to find the error redirect location so would be logic to use the same unwrapped exception as the attribute. |
Still test failures on these, latest build completed 22 minutes ago. com/sun/ts/tests/servlet/spec/errorpage/URLClient.java.heirarchyErrorMatchTest
com/sun/ts/tests/servlet/spec/errorpage/URLClient.java.servletToDifferentErrorPagesTest
com/sun/ts/tests/servlet/spec/errorpage/URLClient.java.wrappedExceptionTest
|
Tossing this in here for reference, this is the code tree for the Jetty 11 (TCK 9.0.0 / Servlet 5.0.1) for these specific tests. https://github.com/eclipse-ee4j/jakartaee-tck/tree/9.0.0/src/com/sun/ts/tests/servlet/spec/errorpage |
Noticed this in the jetty logs.
Pushed a fix for the new XML deployable on commit 81b159b |
The following tests fail on jetty-11:
This is because the tests throw a ServletException wrapping an IllegalThreadStateException and IllegalStateException respectively. Jetty sets the request attributes
jakarta.servlet.error.exception_type
andjakarta.servlet.error.exception
to the ServletException, whereas the tck is testing that they are set to the unwrapped Exception. The servlet spec does not say what they should be set to. I have raised an issue on the servlet-api to clarify what they should be: jakartaee/servlet#388.Note that these tests do not fail on jetty-10, because the earlier 4.0.0 version of the tck had a typo in
javax.servlet.error.exception_type
(was mispelt asjavax.serlvet.error.exception_type
) producing a value of null that the test was then incorrectly testing for, instead of the actual Exception. That was fixed for tck 5.0.0 by jakartaee/platform-tck#254.The text was updated successfully, but these errors were encountered: