Re: Object-oriented encapsulation in Struts - merging Actions and ActionForms

2003-06-24 Thread David Graham
Specifically, what would you change? David --- Dan Jacobs [EMAIL PROTECTED] wrote: [ potentially controversial topic ] Hi all, I have noticed that most of my Struts applications end up being implemented like dismembered objects. I design the controller parts of my Struts applications

RE: Object-oriented encapsulation in Struts - merging Actions and ActionForms

2003-06-24 Thread Dan Jacobs
- From: David Graham [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 8:46 AM To: Struts Users Mailing List Subject: Re: Object-oriented encapsulation in Struts - merging Actions and ActionForms Specifically, what would you change? David --- Dan Jacobs [EMAIL PROTECTED] wrote

RE: Object-oriented encapsulation in Struts - merging Actions and ActionForms

2003-06-24 Thread Jones, Ted
PROTECTED]; 'Struts Users Mailing List' Subject: RE: Object-oriented encapsulation in Struts - merging Actions and ActionForms The kind of change I'm suggesting is not small or incremental. It's pretty fundamental. Suppose you've got an ActionForm that represents the state of some presentation

RE: Object-oriented encapsulation in Struts - merging Actions and ActionForms

2003-06-24 Thread David Graham
encapsulation in Struts - merging Actions and ActionForms Specifically, what would you change? David --- Dan Jacobs [EMAIL PROTECTED] wrote: [ potentially controversial topic ] Hi all, I have noticed that most of my Struts applications end up being implemented like

RE: Object-oriented encapsulation in Struts - merging Actions and ActionForms

2003-06-24 Thread Dan Jacobs
To: Struts Users Mailing List Cc: [EMAIL PROTECTED] Subject: RE: Object-oriented encapsulation in Struts - merging Actions and ActionForms That makes sense ...but wouldn't that break the MVC pattern by moving the Controller function into the Model? Ted Jones Maritz Inc. [EMAIL

RE: Object-oriented encapsulation in Struts - merging Actions and ActionForms

2003-06-24 Thread Dan Jacobs
:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 11:06 AM To: [EMAIL PROTECTED] Subject: RE: Object-oriented encapsulation in Struts - merging Actions and ActionForms So you want to combine ActionForm and Action to put the behavior with the data? How would you handle the case where

RE: Object-oriented encapsulation in Struts - merging Actions and ActionForms

2003-06-24 Thread El Harouchi, Jaafar [IT]
List' Cc: [EMAIL PROTECTED] Subject: RE: Object-oriented encapsulation in Struts - merging Actions and ActionForms The MVC design pattern is an object-oriented design pattern. It is not inconsistent with object-oriented encapsulation! A Struts ActionForm is not part the model in an MVC

Re: Object-oriented encapsulation in Struts - merging Actions and ActionForms

2003-06-24 Thread Jing Zhou
- Original Message - From: Dan Jacobs [EMAIL PROTECTED] To: [EMAIL PROTECTED]; 'Struts Users Mailing List' [EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 10:39 AM Subject: RE: Object-oriented encapsulation in Struts - merging Actions and ActionForms The kind of change I'm suggesting

RE: Object-oriented encapsulation in Struts - merging Actions and ActionForms

2003-06-24 Thread Dan Jacobs
PROTECTED] Sent: Tuesday, June 24, 2003 12:09 PM To: 'Struts Users Mailing List' Subject: RE: Object-oriented encapsulation in Struts - merging Actions and ActionForms Dan, You could treat the ActionForm similar to Transfer Objects, which is a completely valid pattern. Furthermore

RE: Object-oriented encapsulation in Struts - merging Actions and ActionForms

2003-06-24 Thread Prabhat Kumar (IT)
I've never used it but I believe that the WebWork framework (http://sourceforge.net/projects/opensymphony) is designed in just this way. The action is basically just a JavaBean with an additional execute method. -Original Message- From: Dan Jacobs [mailto:[EMAIL PROTECTED] Sent: