RE: Defining Struts in Terms of PofEAA
Thanks for that Pete. The message you may be referring to was: >Hi all, > >What are the various Design Patterns used in Struts? Links welcome > > >Thanks & Regards, >Prasenjit Narwade. Does that look like it? The response was from the Struts In Action book i.e. (Appendix A). What I am wanting (if it actually is possible - which means that someone familiar with Struts and PofEAA will be able to answer) is the whether some of the PofEAA patterns apply to the elements of the controller layer. Martin refers to the Struts framework briefly as FrontController(344) and TemplateView(350). Thanks Shane > -Original Message- > From: Peter Abbot [mailto:[EMAIL PROTECTED] > Sent: Monday, 20 October 2003 3:47 p.m. > To: Struts Users Mailing List > Subject: RE: Defining Struts in Terms of PofEAA > > I recall a couple of weeks ago somebody responded to a similar question > breaking each component from the struts framework into the matching > design pattern(s). Try searching the list archives for it. > > > Pete > > -Original Message- > From: Shane Mingins [mailto:[EMAIL PROTECTED] > Sent: Monday, 20 October 2003 3:39 p.m. > To: 'Struts Users Mailing List' > Subject: RE: Defining Struts in Terms of PofEAA > > > Hi Martin > > Thanks, but no it didn't ;-) > > I am wondering if (for example) the Action Classes would actually be > considered an ApplicationController(379) as opposed to an Input > Controller which is the term Martin uses for the Controller in the > MVC(330) pattern. > > Or maybe it's a PageController(333)??? > > Cheers > Shane > > > > -Original Message----- > > From: Martin Gainty [mailto:[EMAIL PROTECTED] > > Sent: Monday, 20 October 2003 3:29 p.m. > > To: Struts Users Mailing List > > Subject: Re: Defining Struts in Terms of PofEAA > > > > Shane- > > > > Take a look at > > http://martinfowler.com/eaaCatalog/modelViewController.html > > > > To quote HyperDictionary: > > (MVC) A way of partitioning the design of interactive software. The > > "model" is the internal workings of the program (the algorithms), the > > "view" is how > > the user sees the state of the model and the "controller" is how the > user > > changes the state or provides input. > > > > Hope this helps, > > > > -Martin > > - Original Message - > > From: "Shane Mingins" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Sunday, October 19, 2003 10:20 PM > > Subject: Defining Struts in Terms of PofEAA > > > > > > > Hi > > > > > > I was wondering if someone could be so kind as to define the Struts > > > architecture in terms of the patterns in Martin Fowler's Patterns of > > > > Enterprise Architecture. > > > > > > Is it possible to define the following elements in the controller > > > layer (from Struts In Action): > > > > > > ActionForwards > > > ActionForm Classes > > > ActionServlet > > > ActionMappings > > > Action Classes > > > > > > As I read about input controllers vs application controller and then > > page > > > controllers, I am wondering whether elements of the Struts framework > > fall > > > into these patterns or not? > > > > > > Could some one familiar with both Struts and PofEAA please enlighten > > > > me? > > > > > > Thanks > > > Shane > > > > > > Shane Mingins > > > Analyst Programmer > > > Assure NZ Ltd > > > Ph 644 494 2522 > > > > > > > > > > > > > > > - > > > 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] > > - > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Defining Struts in Terms of PofEAA
I recall a couple of weeks ago somebody responded to a similar question breaking each component from the struts framework into the matching design pattern(s). Try searching the list archives for it. Pete -Original Message- From: Shane Mingins [mailto:[EMAIL PROTECTED] Sent: Monday, 20 October 2003 3:39 p.m. To: 'Struts Users Mailing List' Subject: RE: Defining Struts in Terms of PofEAA Hi Martin Thanks, but no it didn't ;-) I am wondering if (for example) the Action Classes would actually be considered an ApplicationController(379) as opposed to an Input Controller which is the term Martin uses for the Controller in the MVC(330) pattern. Or maybe it's a PageController(333)??? Cheers Shane > -Original Message- > From: Martin Gainty [mailto:[EMAIL PROTECTED] > Sent: Monday, 20 October 2003 3:29 p.m. > To: Struts Users Mailing List > Subject: Re: Defining Struts in Terms of PofEAA > > Shane- > > Take a look at > http://martinfowler.com/eaaCatalog/modelViewController.html > > To quote HyperDictionary: > (MVC) A way of partitioning the design of interactive software. The > "model" is the internal workings of the program (the algorithms), the > "view" is how > the user sees the state of the model and the "controller" is how the user > changes the state or provides input. > > Hope this helps, > > -Martin > - Original Message - > From: "Shane Mingins" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Sunday, October 19, 2003 10:20 PM > Subject: Defining Struts in Terms of PofEAA > > > > Hi > > > > I was wondering if someone could be so kind as to define the Struts > > architecture in terms of the patterns in Martin Fowler's Patterns of > > Enterprise Architecture. > > > > Is it possible to define the following elements in the controller > > layer (from Struts In Action): > > > > ActionForwards > > ActionForm Classes > > ActionServlet > > ActionMappings > > Action Classes > > > > As I read about input controllers vs application controller and then > page > > controllers, I am wondering whether elements of the Struts framework > fall > > into these patterns or not? > > > > Could some one familiar with both Struts and PofEAA please enlighten > > me? > > > > Thanks > > Shane > > > > Shane Mingins > > Analyst Programmer > > Assure NZ Ltd > > Ph 644 494 2522 > > > > > > > > > > - > > 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] - 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]
RE: Defining Struts in Terms of PofEAA
Hi Martin Thanks, but no it didn't ;-) I am wondering if (for example) the Action Classes would actually be considered an ApplicationController(379) as opposed to an Input Controller which is the term Martin uses for the Controller in the MVC(330) pattern. Or maybe it's a PageController(333)??? Cheers Shane > -Original Message- > From: Martin Gainty [mailto:[EMAIL PROTECTED] > Sent: Monday, 20 October 2003 3:29 p.m. > To: Struts Users Mailing List > Subject: Re: Defining Struts in Terms of PofEAA > > Shane- > > Take a look at > http://martinfowler.com/eaaCatalog/modelViewController.html > > To quote HyperDictionary: > (MVC) A way of partitioning the design of interactive software. The > "model" > is the internal workings of the program (the algorithms), the "view" is > how > the user sees the state of the model and the "controller" is how the user > changes the state or provides input. > > Hope this helps, > > -Martin > - Original Message - > From: "Shane Mingins" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Sunday, October 19, 2003 10:20 PM > Subject: Defining Struts in Terms of PofEAA > > > > Hi > > > > I was wondering if someone could be so kind as to define the Struts > > architecture in terms of the patterns in Martin Fowler's Patterns of > > Enterprise Architecture. > > > > Is it possible to define the following elements in the controller layer > > (from Struts In Action): > > > > ActionForwards > > ActionForm Classes > > ActionServlet > > ActionMappings > > Action Classes > > > > As I read about input controllers vs application controller and then > page > > controllers, I am wondering whether elements of the Struts framework > fall > > into these patterns or not? > > > > Could some one familiar with both Struts and PofEAA please enlighten me? > > > > Thanks > > Shane > > > > Shane Mingins > > Analyst Programmer > > Assure NZ Ltd > > Ph 644 494 2522 > > > > > > > > - > > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Defining Struts in Terms of PofEAA
Shane- Take a look at http://martinfowler.com/eaaCatalog/modelViewController.html To quote HyperDictionary: (MVC) A way of partitioning the design of interactive software. The "model" is the internal workings of the program (the algorithms), the "view" is how the user sees the state of the model and the "controller" is how the user changes the state or provides input. Hope this helps, -Martin - Original Message - From: "Shane Mingins" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, October 19, 2003 10:20 PM Subject: Defining Struts in Terms of PofEAA > Hi > > I was wondering if someone could be so kind as to define the Struts > architecture in terms of the patterns in Martin Fowler's Patterns of > Enterprise Architecture. > > Is it possible to define the following elements in the controller layer > (from Struts In Action): > > ActionForwards > ActionForm Classes > ActionServlet > ActionMappings > Action Classes > > As I read about input controllers vs application controller and then page > controllers, I am wondering whether elements of the Struts framework fall > into these patterns or not? > > Could some one familiar with both Struts and PofEAA please enlighten me? > > Thanks > Shane > > Shane Mingins > Analyst Programmer > Assure NZ Ltd > Ph 644 494 2522 > > > > - > 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]
