Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
Date: 5 Jul 2004 13:33:32 -0000
Message-ID: <20040705133332.15058.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: dev@struts.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 29919]  -
    validator is not ideal

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29919>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29919

validator is not ideal

ndeloof@capgemini.fr changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID


------- Additional Comments From ndeloof@capgemini.fr  2004-07-05 13:33 -------
You may ask for help on users-list before creating a new bug ticket.

Form-bean may have only String or boolean attributes. Beeing so, they can handle
exactly what the user typed in his browser, been validated, and display back to
the user for correction.

If some attributes have to be numbers in your application, you should convert in
an Action class (assuming form has allready been validated, you don't have to
cleanly handle convert exceptions) or use PropertyUtils.copyProperties() to
populate a business object having same properties names but typed as int.

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