Available since OmniFaces 1.0

The FacesExceptionFilter will solve 2 problems with exceptions thrown in JSF methods.

  1. Mojarra's FacesFileNotFoundException needs to be interpreted as 404.
  2. Root cause needs to be unwrapped from FacesException and ELException to utilize standard Servlet API error page handling.

Noted should be that this filter won't run on exceptions thrown during ajax requests. To handle them using web.xml configured error pages, use FullAjaxExceptionHandler.


To get it to run, map this filter on the <servlet-name> of the FacesServlet in the same web.xml.



By default only FacesException and ELException are unwrapped. You can supply a context parameter "org.omnifaces.EXCEPTION_TYPES_TO_UNWRAP" to specify additional exception types to unwrap. The context parameter value must be a commaseparated string of fully qualified names of additional exception types.


This context parameter will also be read and used by FullAjaxExceptionHandler.


The FacesExceptionFilter is also configured on this showcase application. To see the proper handling of 404 yourself, try entering a random URL matching the *.xhtml URL pattern of the FacesServlet on this showcase web application. For example, thisdoesnotexist.xhtml. To see the proper handling of FacesException yourself, invoke the "normal request" buttons on the FullAjaxExceptionHandler showcase page. Without the filter, the RuntimeException and SQLException would end up in an generic HTTP 500 error page instead of the one specific to the exception.