[
https://issues.apache.org/jira/browse/EXTVAL-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806449#action_12806449
]
Gerhard Petracek commented on EXTVAL-82:
----------------------------------------
hi rudy,
thx for the additional testing!
but i think the behavior of javax.faces.VALIDATE_EMPTY_FIELDS without extval
shows a major disadvantage.
it's also the behavior of extval < r3. due to the mentioned disadvantage (see
the previous comment) we moved away from this approach.
since it's quite easy to change the default behavior of extval it isn't a big
deal to align the behavior of extval with the default behavior of jsf2 in
combination with javax.faces.VALIDATE_EMPTY_FIELDS.
however, i think you did an important task.
maybe we should create a wiki page to document the differences (+ reasons) and
how to change the default behavior.
regards,
gerhard
> Add the EmptyValueAwareValidationStrategy annotation to the Length and
> Pattern Annotations
> ------------------------------------------------------------------------------------------
>
> Key: EXTVAL-82
> URL: https://issues.apache.org/jira/browse/EXTVAL-82
> Project: MyFaces Extensions Validator
> Issue Type: Improvement
> Components: Property Validation
> Affects Versions: 1.2.3-SNAPSHOT, 2.0.3-SNAPSHOT, 1.1.3-SNAPSHOT
> Reporter: Rudy De Busscher
> Priority: Minor
>
> Adding the EmptyValueAwareValidationStrategy allows in JSF 2.0 that Length
> and Pattern validations are triggered (with the
> javax.faces.VALIDATE_EMPTY_FIELDS parameter set).
> They will cause a validation error with an empty string (Length annotation
> with minimum set or Pattern) so the Required annotation is no longer needed.
> Tested it out with ExtVal 2.0.3-SNAPSHOT and Myfaces 2.0.0-SNAPHOT (of 21/01)
> and it works as expected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
