[
https://issues.apache.org/jira/browse/MYFACES-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887495#action_12887495
]
Oliver Bayer commented on MYFACES-2798:
---------------------------------------
Hi,
sorry for the late reply.
@Michael:
Just an idea: why can't the validation behave the same way so that auto behaves
like "true"?
@Jakob:
I've found this ticket:
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=475
Is this related to the same issue?
What do you think? Is my suggestion in this ticket a legit one or do I ran into
the validator problems only because I'm new to JSF? Would the change of
VALIDATE_EMPTY_FIELDS to true be useful to everyone or can you see some
drawbacks (as the bean validation mentioned above)?
Thanks in advance.
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.
