[
https://issues.apache.org/jira/browse/EXTVAL-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek resolved EXTVAL-82.
------------------------------------
Resolution: Won't Fix
the initial reason for the marker was to avoid such an implicit required
validation.
use-case: a property is not required but if users provide a value it has to
fulfill e.g. a minimal length.
the scenario described in this issue is easy to solve via an additional
@Required constraint at the property or a custom validation strategy (as
replacement for the default one) which hosts the mentioned marker.
> 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.
