meeboo wrote: > > Do you create an action class (e.g. UserAction.java) for all User actions, > or do you separate them into UpdateUser.java/CreateUser.java etc...? >
I am also interested in the community's thoughts on this question. On one hand, having an action class for each use case tends to result in an explosion of action classes in large apps. Furthermore, articles like Ian Roughley's "Migrating to Struts 2" (http://www.infoq.com/articles/migrating-struts-2-part2) and the "Starting Struts 2" book (page 70) seem to advocate for consolidating related actions into on Action class with multiple methods. On the other hand, Struts' zero config support doesn't seem to work unless you keep the use cases separated out into separate Action classes. I really like zero config ;-) -- View this message in context: http://www.nabble.com/-S2--Design-patterns-tf3901386.html#a11062286 Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
