[
https://issues.apache.org/jira/browse/MYFACES-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792192#action_12792192
]
Jakob Korherr commented on MYFACES-2454:
----------------------------------------
I came up with the following solution for the backwards compatibility:
- org.apache.myfaces.ERROR_HANDLING will be dismissed by MyFaces 2.0, because
we will always handle the Exception with the ExceptionHandler (the spec tells
us to).
- org.apache.myfaces.ERROR_HANDLER can still be used, but only in conjunction
with javax.faces.webapp.PreJsf2ExceptionHandlerFactory. However, only the
method handleException(FacesContext context, Exception e) has to be provided.
> Adapt default error page generation to new spec
> -----------------------------------------------
>
> Key: MYFACES-2454
> URL: https://issues.apache.org/jira/browse/MYFACES-2454
> Project: MyFaces Core
> Issue Type: Task
> Components: JSR-314
> Affects Versions: 2.0.0-alpha-2
> Reporter: Jakob Korherr
>
> see spec section »6.2.3 Default Error Page« for details.
> This includes the following tasks:
> - <ui:include src="javax.faces.error.xhtml" /> should include the standard
> error page (created by _ErrorPageWriter in MyFaces) in any facelet error page
> defined in web.xml
> - <error-page> entries in web.xml should take priority over MyFaces' default
> error page (currently you have to disable it via
> org.apache.myfaces.ERROR_HANDLING first)
> - UIInput should create an UpdateModelException and publish it, if an
> exception occurs in updateModel()
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
