One thing I'm not clear on for Struts2 action classes is how many there should be per action. For example, lets assume I have a group of 3 related actions: list a set of records, delete a record, add a record. Should that be setup as one action class or 3? I found tutorials which show how to setup a struts.xml to do it with one action class such as:
But is this a good practice? It seems like its random which command could be considered "execute()". Is it ok to not have an execute command?
That Depends. Personally, I like to keep CRUD methods together and have a naming convention so I can easily trace the execution flow like so:
CustomerAction -> CustomerLogic -> CustomerDAO -> CustomerTableInDatabase
There's nothing inherently wrong with creating seperate actions for CRUD functions.
Scott Selikoff wrote:
Is it ok to not have an execute command?
Sure. That's a welcome feature in Struts 2 as opposed to Struts 1