|
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
strategies?
For instance, in the demo we display/update
coporate Address information on the Order form, on the Account
Maintenance form and also in a popup (independent) form. Now it
seems silly to have three sets of form/action classes to manage the same
data (at least we only use one EJB ;>)
Advice?
Thanks...Steve
|
- Re: code reuse Steve LeClair
- Re: code reuse Ted Husted
- RE: code reuse Stephen LeClair
- Re: code reuse Ted Husted
- Re: code reuse Steve LeClair

