struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Birch <alex_d_bi...@yahoo.co.uk>
Subject RE: Struts Community is going crazy! :-))
Date Tue, 20 Aug 2002 16:14:55 GMT
Yes...sorry I don't think I made myself quite clear... I am aware that ActionForms are created
on
a per-request basis... what I was pointing out was that the "one per screen" colour that is
associated with the ActionForm comes under the "Number of Implementations (in general)" legend.
This would imply that there is an implementation of an ActionForm class per screen. The square
outline colours represents instances in memory which would more accurately describe how they
are
generated. The Action class for instance has a "one per action" colour.

Perhaps I am wrong in my interpretation but what I was stating was that it was ambiguous and
could
be interpretted in more ways than one

Alex

 --- Jason Rosen <JRosen@yvimail.com> wrote: > Dan's diagram actually (and correctly)
denotes that
there is one ActionForm
> instantiated per request or session (depending on the scope it is configured
> for in the ActionMapping).  The same ActionForm class can be configured for
> multiple Actions via the ActionMapping, as you stated, but the ActionForm
> object is instantiated from the class once per request or session for the
> particular Action that uses the ActionForm.  Therefore, 2 different Actions
> can use the same ActionForm class and cause the RequestProcessor to
> instantiate the ActionForm object from the ActionForm class.
> 
> When the Action is requested by a client, the RequestProcessor will check to
> see if an instance of the ActionForm exists in the request or session (can't
> remember the request/session attribute keys that it is stored under), if it
> does not exist, it is created and any request parameters sent by the client
> are populated into the appropriate ActionForm properties (see
> RequestProcessor.processActionForm for details).
> 
> So, if 100 clients concurrently request an Action that has an ActionForm
> configured for request scope, there will be 100 instances of the ActionForm
> (one for each client).  Once the request delivers a response, the request
> object is "destroyed" (waiting to be garbage collected) along with the
> ActionForm instance.
> 
> Jason
> 
> -----Original Message-----
> From: Alex Birch [mailto:alex_d_birch@yahoo.co.uk]
> Sent: Tuesday, August 20, 2002 7:28 AM
> To: Struts Users Mailing List
> Subject: RE: Struts Community is going crazy! :-))
> 
> 
> Dan,
> 
> that is a fantastic diagram (so much information so easily accessible in
> such a small place)!
> 
> I have one question though to do with the ActionForm...
> 
> Your colouring infers that there is one 'ActionForm per screen'. I know that
> an ActionForm
> instance is created (and filled with the form information from the client)
> whenever a form-bean is
> specified in the struts-config.xml, but I have read many discussions which
> state it sometimes can
> be more useful to make a less granular ActionForm class which encompasses
> many forms across
> different pages. This could be a little confusing on your diagram (then
> again, maybe it's just
> me!). Did I interpet things incorrectly?
> 
> Alex
> 
>  --- Dan Cancro <DCancro@bridgespan.com> wrote: > This may or may not be
> what you're looking for,
> but I've been trying to
> > organize patterns in the following diagram that's meant to show, among
> other
> > things, where all the routine http request sub-activities should be coded.
> > I color coded the activities to identify those that can be coded in more
> > than one place and so contribute to potentially chaotic designs.  I'll
> look
> > over Ted's patterns and see how I can add some of that stuff to the
> diagram.
> > 
> > http://members.telocity.com/dcancro/images/eng/Struts_MVC.gif
> > 
> > 
> > Dan
> > 
> > --
> > To unsubscribe, e-mail:
> <mailto:struts-user-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail:
> <mailto:struts-user-help@jakarta.apache.org>
> >  
> 
> __________________________________________________
> Do You Yahoo!?
> Everything you'll ever need on one web page
> from News and Sport to Email and Music Charts
> http://uk.my.yahoo.com
> 
> --
> To unsubscribe, e-mail:
> <mailto:struts-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
> <mailto:struts-user-help@jakarta.apache.org>
> 
> --
> To unsubscribe, e-mail:   <mailto:struts-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:struts-user-help@jakarta.apache.org>
>  

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

--
To unsubscribe, e-mail:   <mailto:struts-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@jakarta.apache.org>


Mime
View raw message