Here's the new issue with validations:
https://issues.apache.org/jira/browse/TRINIDAD-1195
Stephen Friedrich wrote:
Yup, that part is working in 1.2.9,
But I just noticed a regression: Now the validators (well at least the
length validator)
no longer work correctly when only the minimum is set.
You'll get error messages like "must enter between 3 and 0 character"
and no input
ever validates successfully.
When client side validation is disabled the validation is correct, but
when validation
fails the error message always shows "0" as minimum.
I'll soon file a Jira issue with examples.
Matthias Wessendorf wrote:
Hi,
we had a report for it already:
http://issues.apache.org/jira/browse/TRINIDAD-1129
It should be fixed with the 1.x.9 release
On Fri, Aug 22, 2008 at 11:50 AM, Marco Grimm
<[EMAIL PROTECTED]> wrote:
Hello altogether,
we have a problem with the validators (or only DoubleRangeValidator?)
after
restoreState. When restoreState is executed, new instances for the
validators are created (that is the properties/attributes like
"maximum" and
"minimum" have the default value. When the following validate() is
executed
the org.apache.trinidad.validator.DoubleRangeValidator first tries to
execute super.validate(), which finishes without an exception, but -
here is
the bug - does not validate anything, because the
properties/attributes are
not set.
getMaximum() and getMinimum() would return the correct values,
because they
get the return value from the _facesBean, but the validate()-Method in
javax.faces.validator.DoubleRangeValidator does not use getMaximum() but
maximum (the private attribute, which is not set). If I might give a fix
suggestion, maybe the restoreState(...)-Method in the
DoubleRangeValidator
should additionally execute super.restoreState(...), then the
properties/attributes would be set in the
javax.faces.validator.DoubleRangeValidator.
If my fix suggestion is completely wrong, please execuse me.
Marco Grimm
