You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2010/05/04 22:59:02 UTC
[jira] Resolved: (MYFACES-2697) BeanValidation class is annotated
with @FacesValidator tag
[ https://issues.apache.org/jira/browse/MYFACES-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leonardo Uribe resolved MYFACES-2697.
-------------------------------------
Assignee: Leonardo Uribe
Fix Version/s: 2.0.1-SNAPSHOT
Resolution: Fixed
> BeanValidation class is annotated with @FacesValidator tag
> ----------------------------------------------------------
>
> Key: MYFACES-2697
> URL: https://issues.apache.org/jira/browse/MYFACES-2697
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.0
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
> Fix For: 2.0.1-SNAPSHOT
>
>
> BeanValidation class is annotated with @FacesVallidator annotation, and it should not be.
> We know that by default BeanValidation should be added to the Application object only if the param javax.faces.validator.DISABLE_DEFAULT_BEAN_VALIDATOR is set to false. So, there is no reason to use @FacesValidator, let the scanner find it and then check the property. It is better keep things simple and simplify the code on FacesConfigurator.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.