« Awesome! | Main | The 101 Dumbest... »

Actions part of Controller or Model?

Comments[0] by Dave in Roller
[Struts] developers have a differing opinion on whether the Action class is part of the controller or the model. The argument for it being part of the controller is that it isn�t part of the �real� business logic. If Struts were replaced with an alternative framework, chances are the Action class would be replaced with something else. Therefore, it really isn�t part of the model domain, but rather tightly coupled to the Struts controller. It doesn�t make sense to put business logic into the Action, since other types of clients can�t easily reuse it. From Chapter 3 in the Server Side's Jakarta Struts Book Review Project
In the alternative framework WebWork, the action classes could be considered to be part of the model because they include no presentation specific code (i.e. no Servlet API calls). Some would argue that this is better and allows re-use of actions, but I think it is just different. For Roller, the WebWork approach really does not buy me much - my 'business logic' is already re-usable and encapsulated in my model interfaces and classes.


Like this post?  del.icio.us Bookmark it   |   submit to dig digg.com Digg it   |   slashdot Slashdot it   |   technorati See who links to it

Comments:

Post a Comment:
  • HTML Syntax: Allowed

This work is licensed under a Creative Commons License.
Copyright 2002-2007, David M Johnson (dave.johnson at rollerweblogger.org)

This is a personal weblog, I do not speak for my employer.