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
-
ubject: RE: How to structure a struts2 application
>
>
>
>
> one action per function or functional area is probably best.
>
>
>
> you can then tailor the validation and responses more easily.
>
>
>
> adam
>
>
>
> > Date: Fri, 24
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@strut
Hi,
I have just started learning struts2 and was wondering what is the best way
to structure my application.
I was planning on creating one ActionSupport class to deal with all user
action (creating, editing, login etc). This would have a method for each
type of action (create(), login() etc) and
6 matches
Mail list logo
