Hello,

Not sure if this deserves another thread or if I can attach it to this one.
I'm new to mailing lists so please be kind.  :  )

I'm working on a struts project now and going back and forth on whether to
just have one form for the whole system or have many forms.

In our case we put the common fields in a base form and created other forms
to extend that one. Each of those forms correspond to a specific section in
the system. The problem we're running into now is that we're finding more
and more common items and having to move them into the base form. Which
lead me to think about just having one form and not bothering with the
others.

Comments?




                                                                                       
                                                 
                      "Taylor Cowan"                                                   
                                                 
                      <t.cowan@charter.        To:       "Struts Users Mailing List" 
<[EMAIL PROTECTED]>                   
                      net>                     cc:       (bcc: David Z. 
Pantich/OE/FirstEnergy)                                         
                                               Subject:  Opionions: fine or course 
grained actions                                      
                      02/07/2003 09:19                                                 
                                                 
                      AM                                                               
                                                 
                      Please respond to                                                
                                                 
                      "Struts Users                                                    
                                                 
                      Mailing List"                                                    
                                                 
                                                                                       
                                                 
                                                                                       
                                                 




I wanted to see what others in the struts community think about Action
granularity.  I've coded apps that are -extremely- fine grained, having one
Action per user event, like createPreferencesAction,
deletePreferencesAction, update...etc.  The fine grained approach yields
more than one action per screen, and contention for the struts config file
during development.  In the middle are apps that basically have one action
per screen that handles all the button clicks with a switch if/else block.
That's the moderate approach.  The last style is -extremely- coarse grained
in that there might only be one action for the entire app.  Coarse grained
has worked best for XML/XSLT type work flows and in some other situations.

What do you think about Action granularity, should it be very fine and thus
more "HTTP" like in nature, or more coarse grained having fewer URL's?

Taylor


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

Reply via email to