Right, that's the way I look at it too. I guess you could call it a model or
data centric perspective of the system.   To me personally, any business
system is centered around a logical data model.  I tend to build (grow)
everything from the model out to the view.  

It seems like the perspective you are talking about is to build the system
around each atomic transaction that the system is designed to support.  This
is, to me, also a very valid way of looking at it, but, it seems like you
would end up seeing a whole bunch of trees instead of the entire forest (if
you get my drift).  

I like to be able to start out with a BIG picture and break it down into
smaller pictures until I get the level that I'm comfortable with.  It sounds
like you are more comfortable with a higher level of  (finer grained) detail
in your implementation than I am.  


-----Original Message-----
From: Adam Hardy [mailto:[EMAIL PROTECTED] 
Sent: Thursday, September 25, 2003 10:44 AM
To: Struts Users Mailing List
Subject: Re: [Poll] action mappings


I just find it naturally easier to grasp what is going on with one 
Action and one form bean for each object in my model (and normally one 
factory or 'business delegate') plus a host of mappings.

On 09/25/2003 03:59 PM Mainguy, Mike wrote:
> You don't have to create a different ActionClass for every Operation 
> with the same display/FormBean...  I.E.  If you use the same formbean 
> and display component, you don't want to also always create another 
> ActionClass...
> 
> Similar to dispatchaction except you use the pathmapping instead of 
> the request parameters.
> 
> I actually wrote a variant of dispatchAction that, instead of calling 
> a specific execute method on my ActionClass, it maps the request to 
> another Command style class that performs an operation with only the 
> FormBean and a security context as the input, and a List or DynaBean 
> as the output.  This let me completely decouple my data access layer 
> from any web stuff and use request parameters to determine which 
> business operation I was performing.
> 
> 
> -----Original Message-----
> From: Sgarlata Matt [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 25, 2003 9:54 AM
> To: Struts Users Mailing List
> Subject: Re: [Poll] action mappings
> 
> 
> 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]
> 
> 
> 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]
> 
> 

-- 
struts 1.1 + tomcat 4.1.27 + java 1.4.2
Linux 2.4.20 RH9


---------------------------------------------------------------------
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]

Reply via email to