Re: [Poll] action mappings

[Timo Neumann]

Mainguy, Mike wrote:

I started with #1 but then switched to #2.
As this is my first big struts project I might be wrong but I had the
impression that #2 would be preferrable because with #1 I would have to 
repeat the action mapping as a string in my action classes.
I saw that most of the respondents went with #1 so I wonder why they 
prefer it?

cheers,

Timo

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) ...
--
F&F Computer Anwendungen        Tel: +49 89 51727-352
und Unternehmensberatung GmbH   Fax: +49 89 51727-111
Westendstr. 195                 Mail: [EMAIL PROTECTED]
D-80686 Muenchen                http://www.ff-muenchen.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]