Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <26669216.post@talk.nabble.com>
Date: Sun, 6 Dec 2009 13:22:29 -0800 (PST)
From: nguyenlinh <nguyenlinh.mail@gmail.com>
To: user@struts.apache.org
Subject: Re: RequiredFieldValidator and error message from property file via
  key
In-Reply-To: <74a2042d0912040704i1e4e6583g3ab00c87de8ef88b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <8141dfcc0912040225n2abfb1d6h435533b154d15bfa@mail.gmail.com>
 <74a2042d0912040704i1e4e6583g3ab00c87de8ef88b@mail.gmail.com>


Hello,
I have the same problem. So what kind of validator should I use if I have a
field of type int and I want to make sure the user typed a number?
Thanks,
Linh


Greg Lindholm-2 wrote:
> 
> You may have a different problem then you think;
> 
> The @RequiredFieldValidator does not make any sense on a int
> (primitive) field as an int cannot be null. The validation interceptor
> checks the values on the fields after params interceptor sets the
> fields. The RequiredFieldValidator checks if the field is null which
> will never be the case for a primitive field.
> 
> 

-- 
View this message in context: http://old.nabble.com/RequiredFieldValidator-and-error-message-from-property-file-via-key-tp26640581p26669216.html
Sent from the Struts - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org