[
https://issues.apache.org/jira/browse/MYFACES-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869123#action_12869123
]
Jakob Korherr commented on MYFACES-2697:
----------------------------------------
I will check this again (also against Mojarra) and add some test cases to
verify the behavior!
> 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: Jakob Korherr
>
> 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.
