One approach to building applications that is supported by Struts 1.3+ is to write a commons-chain based application and plug it into Struts, however, that is only one approach while the existing Action class approach still exists and will exist for a very long time. Personally, I favor using either MappingDispatchAction, Struts Flow, or a custom POJO action class ala JSF.
Therefore, Joe's statement is correct. If you never messed with RequestProcessor, the chain-based processor implementation will not affect you. It is kinda confusing, but the chain used for Struts is not the same chain that Ted was talking about, and in fact, I believe we are trying to separate the two to ensure a clean separation between Struts and application logic.
Yes. If I may, what Ted, Vic, Don, and I are saying is that you should treat Struts as an adapter between HTTP requests and an application which has nothing to do with HTTP. Minimal business logic should be embedded in the Struts layer, whether embedded in Actions, ActionForms, or chain Commands. Struts should do input validation, interface flow control, and translation from HTTP request parameters to application objects and from application objects and data to HTML views.
Ted and Vic, in particular, are saying that commons-chain is a good way to write one of these applications-which-has-nothing-to-do-with-HTTP.
In my experience, relevant to this thread, Spring Framework is a pretty nice way to assemble one of these applications-w-h-n-t-d-w-H; I just used a PlugIn to invoke Spring to assemble the application and put it into the Servlet Application Scope. One could certainly use both together, but I haven't had cause to design a big app since I've become more familiar with commons Chain (and I am still quite a novice user of Spring.)
I hope I didn't distort anyone's statements or views!
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
