myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Korherr (JIRA)" <...@myfaces.apache.org>
Subject [jira] Updated: (MYFACES-2615) Conversion errors should add a FacesMessage instead of throwing a FacesException
Date Tue, 23 Mar 2010 13:27:27 GMT

     [ https://issues.apache.org/jira/browse/MYFACES-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jakob Korherr updated MYFACES-2615:
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0-beta-4
           Status: Resolved  (was: Patch Available)

> 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
>             Fix For: 2.0.0-beta-4
>
>         Attachments: MYFACES-2615.patch
>
>
> 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.


Mime
View raw message