I think for #3 it would be silly not to use a DispatchAction or LookupDispatchAction, right? It seems like you would also want DispatchAction or LookupDispatchAction for #1, but I really don't understand why people are using #1 at all. Is there some reason multiple action mappings are needed for the same Action?
Matt ----- Original Message ----- From: "Mainguy, Mike" <[EMAIL PROTECTED]> To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]> Sent: Thursday, September 25, 2003 9:47 AM Subject: RE: [Poll] action mappings > So far the results are as follows: > > #1 5 > #2 1 > #3 2 > #4 0 > > I added myself to both 1 and 3 as I've done a project both ways... Now I > wonder, how does everyone determine which operation you are doing? As a > parameter in the action mapping? A big case-style (if else) statement? > > -----Original Message----- > From: Mainguy, Mike [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 23, 2003 11:06 AM > To: [EMAIL PROTECTED] > Subject: [Poll] action mappings > > > 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] > > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
