[jira] Commented: (MYFACES-2615) Conversion errors should add a FacesMessage instead of throwing a FacesException

["Jakob Korherr (JIRA)" <de...@myfaces.apache.org>]

    [ https://issues.apache.org/jira/browse/MYFACES-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847801#action_12847801 ] 

Jakob Korherr commented on MYFACES-2615:
----------------------------------------

It turns out that this is just a problem of UIViewParameter. All other JSF input components do behave the right way at the moment!

> Conversion errors should add a FacesMessage instead of throwing a FacesException
> --------------------------------------------------------------------------------
>
>                 Key: MYFACES-2615
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2615
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-314
>    Affects Versions: 2.0.0-beta-3
>            Reporter: Jakob Korherr
>            Assignee: Jakob Korherr
>
> While working on MYFACES-2614 I ran into the problem that, if a conversion fails, the error page is displayed with the related ConverterException. This should not happen, instead a FacesMessage describing the conversion error should be added to the FacesContext.
> See section 2.2.3 Process Validations (or also section 2.2.2. Apply Request Values for components with immediate set to true) of the JSF 2.0 spec: "Conversions and Validations that failed will have caused messages to be enqueued via calls to addMessage()...".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.