Re: [S2] Design patterns

2007-06-11 Thread Sami Dalouche
Hi, I personally : 1] Do NOT use inheritance, besides ActionSupport that provides the basic methods (getText, ..) to work with Struts2. 2] Group all methods of a form inside the same Action. Usually, I need the same code to prepare the input and the validation of the form, so why would I bother

Re: [S2] Design patterns

2007-06-11 Thread Kyle Adams
ating 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.nabb

Re: [S2] Design patterns

2007-06-11 Thread Jeromy Evans
I agree with Guru. After you've gained familiarity with S2, you need to consider about what's appropriate for the particular use-cases and business/domain model. As soon as you start repeating yourself in your action/view code you know its time to refactor. Here's some of my approaches: - For

RE: [S2] Design patterns

2007-06-11 Thread Raghupathy, Gurumoorthy
well then either of the above should be fine . Regards -Original Message- From: meeboo [mailto:[EMAIL PROTECTED] Sent: 11 June 2007 13:52 To: user@struts.apache.org Subject: [S2] Design patterns Hey all How do you build up your Struts 2 applications architecture wise? Say for ins

[S2] Design patterns

2007-06-11 Thread meeboo
ationAware and so forth. Do you think this is a good approach? It's worked great for us so far. Cheers! -- View this message in context: http://www.nabble.com/-S2--Design-patterns-tf3901386.html#a11059979 Sent from the Struts - User mailing list archiv