When Glassfish catches a ServletException, it calls getRootCause recursively on each successive unwrapped, nested exception by reflection. This is fine for wrapped ServletException and JspException, which have well-defined semantics for this method, but creates a big problem if you have an application-defined exception that happens to use the same "getRootCause" name with different semantics.
So I created a Glassfish bug report:
http://java.net/jira/browse/GLASSFISH-17390
Related original bug in Tomcat, since fixed:
https://issues.apache.org/bugzilla/show_bug.cgi?id=39088
No comments:
Post a Comment