Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Discussion" <users@myfaces.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
From: "Marco Grimm" <Marco.Grimm@rz-service-mannheim.de>
To: <users@myfaces.apache.org>
Cc: =?iso-8859-1?Q?'Wolfgang_T=F6pfer'?= <wolfgang.toepfer@pta.de>
Subject: [Trinidad] problem with validators (or only DoubleRangeValidator?)
 after restoreState
Date: Fri, 22 Aug 2008 11:50:30 +0200
Organization: DATIS Software GmbH
Message-ID: <7594AA8FE7D24F41A0D7DB407547443A@COMPANY.RZSERVICE.Pri>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Thread-Index: AckEPINXi4pHeSSHSLSiWfd+sR+OtA==

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