-Original Message-
From: Peterkofsky, Don [mailto:[EMAIL PROTECTED]]
--///--
I've been successfully using the Dispatch action in the
development of an
application here, without yet implementing validation. I'm using
DynaValidatorActionForm beans and extending action classes from
? Any assistance/advice is appreciated.
Thanks and regards,
Don Peterkofsky
* From: Ted Husted
* Subject: Re: code reuse
* Date: Sun, 22 Jul 2001 11:54:30 -0700
I would say that if you have one EJB for all these properties, then you
should have one ActionForm as well
]
Subject: Re: code reuse
I would say that if you have one EJB for all these properties, then you
should have one ActionForm as well.
The trick to ActionForm reuse is the validation method. If the class is
used on more than one form, then validate() may need to address a
different set
From your description, it sounds like there could be an ancestor
ActionForm common to the Order and Maintenance wizards. If that were the
case, each could subclass that ActionForm, and the Corporate Info Action
would then refer to the ancestor class, common to both wizards.
In general, an Action
prototype to identify what I'm missing.
Thanks...Steve
- Original Message -
From: Ted Husted [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, July 24, 2001 9:25 AM
Subject: Re: code reuse
From your description, it sounds like there could be an ancestor
ActionForm common to the Order
I would say that if you have one EJB for all these properties, then you
should have one ActionForm as well.
The trick to ActionForm reuse is the validation method. If the class is
used on more than one form, then validate() may need to address a
different set of properties. If you are using the
Our firm is has been using the struts framework to
build our application demos. Now that we are shifting into a development cycle
for a production release, we'd like to know more about how to build the struts
side of our codebase with reuse in mind.
Has anyone collected threads on reuse
7 matches
Mail list logo
