Is there a reason why exceptions that occur during the invoke application phase are handled by the ExceptionFilter rather than by an interceptor? I've subclassed org.jboss.seam.core.Exceptions and registered some of my own ExceptionHandlers to allow conditional redirects based on the viewId, which the MockFacesContext registered by the filter does not provide. I've also noticed that if an ExceptionHandler triggered during invoke application attempts a redirect to a page that includes page parameters you'll get a null pointer exeption because the MockApplication does not include a VariableResolver either. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4076998#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...