Re: [Poll] action mappings

[Ted Husted]

I use ActionMappings to represent a use-case or client story, rather 
than an atomic operation. The form-bean and validator collect the data 
the story needs, and an Action passes those to the business layer, and 
return the outcome. The business layer class is specified as a parameter 
so that I can reuse the same standard Action for most stories.

So, I suppose my answer to this poll is I don't use ActionMappings for 
CRUD operations. I keep the CRUD crud between the business layer and the 
data access objects. Unless, of course, create/retrieve/update/delete 
were stories from the client's perspective :)

I imagine you've seen this, but ...

http://www.mail-archive.com/[EMAIL PROTECTED]/msg57843.html

The work on the Commons Chain is coming along nicely, and we should see 
some standard Command Actions showing up that just pass a context up the 
business layer and then pass it back to the presentation layer. So, 
before long, I suspect people will be talking less about Actions and 
more about business layer Commands and Command Chains.

-Ted.

Mainguy, Mike wrote:

I have yet another opinion poll for struts-user...

What are folks currently doing for action mappings in relation to CRUD
operations?  
Are you:

#1  creating a unique Action mapping for each atomic operation 
    (potentially mapped to the same action class)
	/createUser.do     ->>  UserAction.java
	/readUser.do       ->>  UserAction.java
	/updateUser.do     ->>  UserAction.java
	/deleteUser.do     ->>  UserAction.java
	

#2  creating a unique Action mapping for each atmoic operation 
    with each action having a unique class
	/createUser.do     ->>  CreateUserAction.java
	/readUser.do       ->>  ReadUserAction.java
	/updateUser.do     ->>  UpdateUserAction.java
	/deleteUser.do     ->>  DeleteUserAction.java

#3  creating an aggregate action class with a unique action mapping with 
    multiple operations and using form/request variable to accomplish CUD
	/editUser.do       ->> UserAction.java   (?OP=Update, ?OP=Create,
?OP=Delete)
	/displayUser.do    ->> UserAction.java

#4  creating an aggregate action class with a unique action mapping with 
    multiple operations
	/editUser.do       ->> EditUserAction.java   
	/displayUser.do    ->> DisplayUserAction.java

Some other way (or a combination) ...

  

This message and its contents (to include attachments) are the property of Kmart Corporation (Kmart) and may contain confidential and proprietary information. You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on information contained herein is strictly prohibited. Unauthorized use of information contained herein may subject you to civil and criminal prosecution and penalties. If you are not the intended recipient, you should delete this message immediately.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

--
Ted Husted,
  Junit in Action  - <http://www.manning.com/massol/>,
  Struts in Action - <http://husted.com/struts/book.html>,
  JSP Site Design  - <http://www.amazon.com/exec/obidos/ISBN=1861005512>.
"Get Ready, We're Moving Out!!" - <http://www.clark04.com>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]