Since I have moved to struts 2, It has been somehow hard for me to forgo the
simplicity offered by combining struts 1.2+ and Apache common chains. In a
number of projects [medium sized to large] I managed to get away only with ONE
single action class for the whole project. Just consider the following:
1- All your http forms use a Map form
2- Each of your url mappings maps to a chain name
3- You have a single CommandAction class that does the following:
a) Puts the Map form in a chain context
b) Executes the chain
c) Iterates through the context and puts every value whose key
conventionally starts with "request_"
c) forwards the result
I have been trying to see if I can devise or follow a similar logic in struts 2
but so far of no avail, and I have ended up creating actions here and there.
Though "Struts in Action" book touchs on a few designs for CRUD, It falls below
the flexibility and the simpilicity offered by struts 1.2+ and command chains
in this respect. I was just wondering if anybody else out there has any
ideas/tips that can share in this regard?
__________________________________________________________________
Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your
favourite sites. Download it now at
http://ca.toolbar.yahoo.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
