ActionForms allow non-string properties?
Well firstly for dealing with nested forms, collections of nested
forms and
the like.
One also needs to remember that the ActionForm is an object that
represents
the state of the UI - and depending on what you are doing you may
wish to
use it for storing information
, 2003 11:55 PM
To: Struts Users Mailing List
Subject: RE: Why do ActionForms allow non-string properties?
Well firstly for dealing with nested forms, collections of nested
forms and the like.
One also needs to remember that the ActionForm is an object that
represents the state of the UI
Though, there is still a ton maintenance going on here. We have the
properties defined in the HTML form, and the struts-config, and in the
validator.xml, and then in some type of corresponding property in the
business bean, not to mention the actual data store. So to add a
field, we have
We look forward to your patches =:0)
Get them in this morning, and I should be able to apply them tonight.
Andrew Hill wrote:
Well, I think it a bit restrictive to forbid non-string properties, but I
would say that the docs really ought to make it clear that the recommended
type for all those
Still,
there's
so much custom stuff (label taglib, javascript pop-up
calendars) that I
put
into forms, I doubt this will ever be possible.
It's called a code generator and its already been done
in other environments. The trade-off is that you lose
some of the really fine control that is so
) objects and using
basic flat String based (non-nested) forms.
Brandon Goodin
-Original Message-
From: Lynn Guy [mailto:[EMAIL PROTECTED]
Sent: Friday, May 30, 2003 10:10 AM
To: Struts Users Mailing List
Subject: RE: Why do ActionForms allow non-string properties?
Still,
there's
so much
Well, I think it a bit restrictive to forbid non-string properties, but I
would say that the docs really ought to make it clear that the recommended
type for all those properties that directly relate to html controls should
be strings.
-Original Message-
From: Steve Raeburn [mailto:[EMAIL
In what way would it be restrictive? Is there any reason you would need a
non-string property (for html input) ?
Steve
-Original Message-
From: Andrew Hill [mailto:[EMAIL PROTECTED]
Sent: May 29, 2003 11:26 PM
To: Struts Users Mailing List
Subject: RE: Why do ActionForms allow non
)
String getCeoSalary()
setCeoSalaryBigDecimal(BigDecimal ceoSalary)
BigDecimal getCeoSalary()
-Original Message-
From: Steve Raeburn [mailto:[EMAIL PROTECTED]
Sent: Friday, 30 May 2003 14:40
To: Struts Users Mailing List
Subject: RE: Why do ActionForms allow non-string properties?
In what
[mailto:[EMAIL PROTECTED]
Sent: May 29, 2003 11:55 PM
To: Struts Users Mailing List
Subject: RE: Why do ActionForms allow non-string properties?
Well firstly for dealing with nested forms, collections of nested
forms and
the like.
One also needs to remember that the ActionForm is an object
and expecting a query return with a precision limited to 2.
Mark
-Original Message-
From: Andrew Hill [mailto:[EMAIL PROTECTED]
Sent: Friday, May 30, 2003 2:55 AM
To: Struts Users Mailing List
Subject: RE: Why do ActionForms allow non-string properties?
Well firstly for dealing with nested
!
Steve
-Original Message-
From: Andrew Hill [mailto:[EMAIL PROTECTED]
Sent: May 29, 2003 11:55 PM
To: Struts Users Mailing List
Subject: RE: Why do ActionForms allow non-string properties?
Well firstly for dealing with nested forms, collections of nested
forms and
the like.
One also needs
12 matches
Mail list logo
