> Along the lines of best practices, it might be a good idea to use > Actions as entry points and encapsulate business logic in POJOs, which > would allow you to re-arrange them however you need without having to > call back through the ActionInvocation with all of the Interceptors, > etc.
I agree that this would be a good practice. An equally good practice would be to use the actions as commands. Actions represent view independent business logic and encapsulating the business logic in the action means you don't need to write wrapper code. With struts, I absolutely agree that you pretty much need to wrap Struts Actions around POJOs. Struts requires your application be too tied to the web layer. One of WebWork's beauties, IMHO, is that it is relatively view unaware. This makes it an ideal to encapsulate business logic. My personal opinion is that the web layer should be a thin as possible. I love that WebWork2 allows the web layer to be encapsulated in xwork.xml -- Matt Ho Principal Indigo Egg, Inc. http://www.indigoegg.com/ ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
