how understanding outrageous struts actions?
i hereditary enormous leave java web app controlling struts 1.2.4. i have specific doubt per actions. many pages have accurately action, processexecute() methods abominable monsters (very enlarged tons nested statements formed ask parameters).
given actions an doing management pattern, i'm pondering separate actions movement per user gesture. infinite refactoring though, i'm wondering:
- is right direction?
- is there an middle step i take, settlement deals disaster inside monolithic actions? maybe another management settlement inside action?
Comments
Post a Comment