You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by James Turner <tu...@blackbear.com> on 2002/07/09 05:37:03 UTC
RE: DynaActionForm Advantages
My two cents on the topic.
As mentioned, once you move to a good Java IDE like JBuilder, writing
getters and setters is no longer nearly the pain it used to be.
What bothers me about the DynaBean approach is that it's *yet another*
file, and *yet another* level of indirection that obscure what's really
going on. I can look at an ActionForm, see all the properties, look at the
validation, all in one step. Making it a DynaBean form means having to
maintain another file with the XML, always having to remember where it is, etc.
I think the decision to use one or the other is a matter of programming
style, but I don't think either one is dogmatically a best practice.
James
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: DynaActionForm Advantages
Posted by Andrew Hill <an...@gridnode.com>.
+1
-----Original Message-----
From: James Turner [mailto:turner@blackbear.com]
Sent: Tuesday, July 09, 2002 11:37
To: struts-user@jakarta.apache.org
Subject: RE: DynaActionForm Advantages
My two cents on the topic.
As mentioned, once you move to a good Java IDE like JBuilder, writing
getters and setters is no longer nearly the pain it used to be.
What bothers me about the DynaBean approach is that it's *yet another*
file, and *yet another* level of indirection that obscure what's really
going on. I can look at an ActionForm, see all the properties, look at the
validation, all in one step. Making it a DynaBean form means having to
maintain another file with the XML, always having to remember where it is,
etc.
I think the decision to use one or the other is a matter of programming
style, but I don't think either one is dogmatically a best practice.
James
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: DynaActionForm Advantages
Posted by Jacob Hookom <ho...@uwec.edu>.
I agree with James on the extra level aspect. I've been finding that
the finer the granularity in my struts application, the easier it is to
maintain [for each action, a specialized form/bean].
I did opt though for the validator, since it brought regexp validation
to the table which is invaluable and fairly easy to setup in an
afternoon.
Jake
-----Original Message-----
From: James Turner [mailto:turner@blackbear.com]
Sent: Monday, July 08, 2002 10:37 PM
To: struts-user@jakarta.apache.org
Subject: RE: DynaActionForm Advantages
My two cents on the topic.
As mentioned, once you move to a good Java IDE like JBuilder, writing
getters and setters is no longer nearly the pain it used to be.
What bothers me about the DynaBean approach is that it's *yet another*
file, and *yet another* level of indirection that obscure what's really
going on. I can look at an ActionForm, see all the properties, look at
the
validation, all in one step. Making it a DynaBean form means having to
maintain another file with the XML, always having to remember where it
is, etc.
I think the decision to use one or the other is a matter of programming
style, but I don't think either one is dogmatically a best practice.
James
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.373 / Virus Database: 208 - Release Date: 7/1/2002
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.373 / Virus Database: 208 - Release Date: 7/1/2002
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>