[
https://issues.apache.org/jira/browse/MYFACES-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794947#action_12794947
]
Leonardo Uribe commented on MYFACES-2454:
-----------------------------------------
I committed this patch. But after take a look at it again (and the committed
solution) it seems maybe we should not dismiss the init parameter
org.apache.myfaces.ERROR_HANDLING. The reason why is because "....to fully
disable any error handling...." is a very common case (many messages on users
and dev list are probe of it). It is more simple to set this param than write a
custom ExceptionHandler.
> 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
> Attachments: myfaces-2454.patch
>
>
> 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()
> - The error page should also include the view and the flash scope attributes
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
