You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Puneet Agarwal <pu...@delhi.tcs.co.in> on 2003/07/28 08:27:44 UTC
Re: Design in Struts
Raj,
As per the best practice observation, it has always been suggested by
people to have two actions associated with all your screens( considering
one form per screen) . First one to load the page, and the other to process
it.
But in case like ours we could have ended up with too many actions. So we
created one action class that is invoked for preloading excersise of all
screens.
So for all our screens we have a common action class that is invoked to
launch the screen and this action class forwards the request to approprite
page. Adn then we have one action class associated with every screen.
(mostly)
Hope it answeres your q.
Regards,
Puneet Agarwal
Tata Consultancy Services,
C-56, Phase - II, NOIDA 201305 (India)
Phone: +91-120-2461001, 2, 7, 8, 9, 12, 13 (Ext. 1031)
FAX : +91-120-246 1521
Struts ... Action ... Struts in Action ... Action in Struts ...
rajendra.x.yadav@v
erizon.com To: struts-user@jakarta.apache.org
cc:
03/18/02 09:15 AM Subject: Design in Struts
Please respond to
"Struts Users
Mailing List"
Hi All,
I need some guidance about the design prespective of a Web Application
using Struts.
Is it advisable to have a Action with each Form?
If not, then How to have a single action for all your forms and do some
sort of redirection internally ?
thanks
-raj
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org