struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Darren Karstens <>
Subject How to structure a struts2 application
Date Fri, 24 Sep 2010 09:35:42 GMT
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 a mapping with a wildcard like
<action name="*User" class="" method="{1}">

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 validation depending
on which action has been called, or perhaps just having different action
classes for each type of user action. Do either of these approaches sound
sensible? Or am I missing an easier way to go about grouping up all the user

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message