The first route is to implement the business logic in a separate class, for example PollManager. Actions are then used to bridge the web frontend and call methods on the class. Every action that needs PollManager could retrieve it via IoC.
The second route would be to implement the logic inside Actions. In this case, actions would have direct access to the core components, such as the PersistentManager to perform CRUD operations.
Any suggestions and/or opinions?
Cheers, matthew
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork