[EMAIL PROTECTED] wrote:
> beans. Each JSP page has a bean that holds its data. The data is
> contained in a list of PageField objects. The PageField has
> getFieldValue() and setFieldValue() methods that return and take Strings
> respectively. The PageField also has a mapping that will map th
On Tue, 9 Jul 2002 [EMAIL PROTECTED] wrote:
> Date: Tue, 9 Jul 2002 12:21:44 -0500
> From: [EMAIL PROTECTED]
> Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: RE: DynaActionForm Advantages (A different approach)
>
> Somethi
> The preferences for Strings in form beans is to deal with bad
> user input
> (such as typing "1a3" into a text field destined to be an
> integer). Any
> solution that does not redisplay the bad data that the user
> typed (just
> like every GUI program in the world does it) is not acceptable,
2002 12:33 PM
> To: 'Struts Users Mailing List'
> Subject: RE: DynaActionForm Advantages (A different approach)
>
>
> How does your PageField list handle iterative and nested
> properties? Can a
> PageField's value be a String array?
>
> > -Origi
: RE: DynaActionForm Advantages (A different approach)
>
>
> Something that has always bothered me in Struts is the "disconnect"
> between Form Beans and Model Beans. How many times do you have a Form
> Bean and a model bean that contain the same data? The
> disconnect mak
Something that has always bothered me in Struts is the "disconnect"
between Form Beans and Model Beans. How many times do you have a Form
Bean and a model bean that contain the same data? The disconnect makes
some sense because you want everything that could come in from a JSP
page to be String-
6 matches
Mail list logo
