On 9/9/05, Marco Mistroni <[EMAIL PROTECTED]> wrote: > This answer is from my point of view.... Following Ted's example, > All my business logic is now in the Command.. all action does Is simply > To build context and pass it to the command.. so code in action is really > very simple..
I think Marco has hit on an important point. You can write the business side of your application with Commons Chain regardless of what Struts is doing. Likewise, Struts can use Commons Chain for it's internal logic regardless of what your application is doing. There should be a clean separation between the Struts presentation layer and your application. I believe some people are looking at the use of Commons Chain by Struts as a way to continue the HTTP request up into the business layer. Personally, I think that's a misstep. Struts should collect values for your business logic to process. The role of the Action is to provide a place where the presentation layer can exchange values with rest of the application. I've been using a C# port of Commons Chain extensively for over a year now, and it's working quite well for us. We find that a Chain of Responsiblity is very easy to unit test, so we are able to test the business layer before plugging it into the presentation layer. -- HTH, Ted. http://www.husted.com/poe/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
