myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias Wessendorf" <>
Subject Re: [Trinidad] problem with validators (or only DoubleRangeValidator?) after restoreState
Date Tue, 26 Aug 2008 18:12:37 GMT

we had a report for it already:

It should be fixed with the 1.x.9 release

On Fri, Aug 22, 2008 at 11:50 AM, Marco Grimm
<> 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

Matthias Wessendorf

Need JSF and Web 2.0?

further stuff:
mail: matzew-at-apache-dot-org

View raw message