This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I guess that depends to a certain extent on what you do in your actions. I guess they could be considered either. If you use them to simply invoke a session facade in your distributed application, I would consider them part of the controller. Whereas if you start maniuplating your object model and accessing the RDBMS you could say that the action is part of the model. It is probably cleaner to consider them part of the controller and implement the business logic elsewhere where reuse is more likely. Jesse
---<br />Time flies like an arrow,<br />Fruit flies like a banana
Hi Pradeep, the Struts Actions form definitively the Controller part. It is technically possible to add Model logic in the Action. But as Jesse mentioned, it is advaisable to avoid to do so! Regards Berny Woehrlin
Personally, I consider everything in the Action package (and Config package in 1.1) to be part of the control layer, including the ActionForms. The Action is designed to provide a bridge between the presentation layer (JSPs, templates, XMLs) and the model layer. The idea is that the view layer can talk to the Action and the Action then talks to the model layer. Ideally, the Action should be talking to a facade that condenses what it needs to know about the model layer. For example, anything involving JDBC should be behind a facade. The Action passes the required inputs to the facade, and then relays the output to the view. HTH, Ted.
<a href="http://husted.com/struts/book.html" target="_blank" rel="nofollow">Struts in Action</a>
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com