[
https://issues.apache.org/jira/browse/MYFACES-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886337#action_12886337
]
Oliver Bayer commented on MYFACES-2798:
---------------------------------------
Thanks for your quick responses.
Ok, I don't know it's a must-have because of the spec.
I just thought it would reduce the confusion -at least for me :-)- why someone
doesn't get an error although the input field is marked as a required one. With
the spec default to "auto" the <f:validateRequired> tag doesn't make much sense.
But then I don't understand (maybe I should read the spec one day) why the
default is "auto" and not "false".
Since I realised during debugging why the validation isn't called I set the
param in web.xml explicitly so it's not a problem for me.
If you have to stick real close to the spec you can close this ticket otherwise
setting it to "true" would be more intuitive and user-friendly.
Greets Oli
> 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.
