sorry to be pedantic but I wasn't sure about wizard or operation :) I don't quite know how to categorize its 'number of implementations' multiplicity - I've thought about it a fair bit too!
the only thing I could think of was another colour altogether and call it: "One per form or collection of forms" and that's not very good due to the ambiguities with java.util.Collection!! Seeing as DynaActionForm means you don't need to implement any ActionForm classes the situation is even more complex! sorry I could only point it out and not solve it. > I'm so happy you found it useful. Good catch about the ActionForm. I > thought about that and added "(in general)" after "Number of > implementations" because you are right that there could be one ActionForm > implementation for a whole wizard composed of several pages. I'll add a new > background color meaning "One per screen or wizard". Do you think this > would clear up any confusion? Maybe "operation" instead of "wizard". > > Thanks, > Dan > > > -----Original Message----- > > From: Alex Birch [mailto:[EMAIL PROTECTED]] > > 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 <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED]> > > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > > __________________________________________________ > > 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:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > __________________________________________________ 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:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
