[
https://issues.apache.org/jira/browse/MYFACES-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887544#action_12887544
]
Michael Kurz commented on MYFACES-2798:
---------------------------------------
I guess the EG made this decision to have the new behavior (validate on empty
fields) for bean validation and the old behavior (do not validate empty fields)
for standard JSF validation. This guarantees high compatibility for existing
applications.
Changing the default value to true would not be a real problem but it would
change the default behavior in JSF 2.0 compared to JSF 1.2.
> javax.faces.VALIDATE_EMPTY_FIELDS default should be 'true'
> ----------------------------------------------------------
>
> Key: MYFACES-2798
> URL: https://issues.apache.org/jira/browse/MYFACES-2798
> Project: MyFaces Core
> Issue Type: Improvement
> Components: General
> Affects Versions: 2.0.2-SNAPSHOT
> Environment: Win XP, JDK 1.6.0.20, Maven 2.2.1, MyFaces trunk
> Reporter: Oliver Bayer
>
> First I thought the validation tags like e.g. <f:validateRequired /> or
> <f:validateLength /> aren't working. But during debugging I found out that
> the respective validation classes are called if at least one char is inserted.
> At the myfaces homepage
> (http://myfaces.apache.org/core20/myfaces-impl/webconfig.html) I've found
> that the default is "auto".
> I think it would be better to set the default to "true" because one would
> expect to get an exception if he leaves a required field blank which isn't
> the case if it's set to "auto".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
