This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
This jsp doesn't redirect to the servlet ExceptionHandler (it redirects to the tomcat default page 500). You need to remove appbase.jar and all jsf lines in web.xml to succeed. Test.jsp contains : <% try { String s=null; s.length(); } catch(Exception e) { e.printStackTrace(); throw new javax.faces.FacesException(e); } %>
Created attachment 54901 [details] Test.jsp
I don't know exactly how the error page redirect works. Winston is the one worked on this tack. Winston, could you please look into it? BTW, I don't think this is a P1, not a showstopper!
I mark it as P1 because I cannot release a real web application without a custom error page !
Do you have your own custom error handler or still depend on com.sun.errorhandler.ExceptionHandler. If so somehow I noticed that ErrorHandler library was not added to the project. You need to manually add via project library nodes.
errorhandler.jar is added to my project. Even with a simple jsp error page it doesn't work.
Could you please attach the complete log in your server log
Created attachment 54990 [details] Log file when the redirect process fails
Created attachment 54991 [details] Log file when the redirect process succeeds (without appbase.jar)
Thanks for the attachments. I will look at it further
Per the bug priority guidelines, I don't think this qualifies as a P1. Winston, if you agree, please downgrade to P2. thanks
I agree. It does not qualify as P1. Downgrading to P2. I'm continue looking at the problem though.
This seems like a JSF 1.2 issue. I did some experiment. If I have any jar with faces-config.xml then redirecting to error page it fails If I remove the FacesSerlet from web.xml (even with jar with faces-config.xml ex. appbase) it succeeds. I'll work with Ryan Lubke (JSF RI eng) to find out, if this is a issue wit JSF 1.2
I noticed that it is also a bug of JSF 1.1 with netbeans 6.
I'm still investigating the problem. Meanwhile here is a work around Add the following to your web.xml <error-page> <error-code>500</error-code> <location>/error/ExceptionHandler</location> </error-page>
I've filed a bug against JSF https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=703
Created attachment 57231 [details] Attaching a Test Project that depicts the JSF issue with out any Visual Web artifacts
Workaround is available and issue seems to be with JSF. Lowering to P3 for the NetBeans release until new information indicates otherwise.
As per the comment (the test attached without visualweb artifacts), this is not a visualweb issue. Passing to web.
It's a web/jsf placeholder issue and is depending on, https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=703
.
NetBeans.org Migration: changing resolution from LATER to WONTFIX