On Fri, 12 Mar 2004 10:30:08 -0600, Hookom, Jacob wrote:
> <mapping uri="/*">
> <action execute="#{applicationController.validateLogin}" /> <catch
> exception="com.mckesson.smo.AuthorizationException" /> <form id="C"
> /> </mapping>This reminds me of the Maverick approach, which is both simple and effective. > Just some ideas... I've been working on developing a mock version > of this between projects at work. What I would like to do is develop Struts 2.0 test-first. The idea being we cold start with a simple application and write just enough of 2.0 to develop the first page (or story). Then just enough to develop the second page, and so forth. Each component developed would have to be fully testable outside of a servlet/portlet/soap environment. Of course, no one application can represent all of the use cases a framework like Struts must support, so after an initial sample application,we could start on the Struts Cookbook application Steve Raeburn suggested. A very important point being that no feature would be added without conventional unit tests and a working example use case. In doing this, I wouldn't feel constrained to anything we put on the whiteboard, so we could try this or that in the context of working examples. Right now, I'm refactoring the MailReader application in hope of using it as the test-first foundation for Struts 2.0, and also exploring how other frameworks are solving similar problems. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
