Thanks for the responses. The validation interceptor seems to be
exactly what I was looking for.
Regards
Darren
> You don't need multiple classes. The validate interceptor, as the prepare
> one, is very flexible in this sense. You can define multiple validate
> methods inside a single action class
Hi Darren,
> However im not sure if this is the best way of doing things because all of
> the user actions would share the same validate method, and each different
> type of action would need different validation. I was thinking of maybe
> putting a switch in the validate method to do different va
It is also worth pointing out that because Struts2 creates the action on each
call, you don't actually save anything by having a single action for CRUD. You
might actually be worse off by performing unneccsessary activities at times.
Regards
-
s better placed in a service object rather than
the action, reserving the action class purely for view
level handlers only.
> -Original Message-
> From: adam pinder [mailto:apin...@hotmail.co.uk]
> Sent: Friday, September 24, 2010 10:31 AM
> To: user@struts.apache.org
> S
one action per function or functional area is probably best.
you can then tailor the validation and responses more easily.
adam
> Date: Fri, 24 Sep 2010 10:35:42 +0100
> Subject: How to structure a struts2 application
> From: darrenkarst...@gmail.com
> To: user@struts.apache.org
>
5 matches
Mail list logo
