> -----Original Message----- > From: Ted Husted [mailto:[EMAIL PROTECTED] > Sent: 13. oktober 2004 16:13 > To: Struts Developers List > Subject: RE: Roadmap > > On Wed, 13 Oct 2004 12:53:10 +0100, Pilgrim, Peter wrote: > > I think we need to define a feature common denominator table of > > what constitutes a request and response as we know they exist now. > > I'm of like mind, but I'd like to take a step farther back > and define a set of Struts use case scenarios, for both this > generation and the next. > > > (0) Client submits request > > (1) System receives the incoming request > > (2) System transfers matching values to a form object > > (3) System > > validates the object > > (4) System branches to success or failure. > > (4a) On success, system executes/delegates the business logic. > > (4b) On failure, system returns the faulty input. > > (5) A view displays the nominal result or redisplays faulty input. > > And so on. > > Then we'd have a clear idea of what we are building the > interfaces to do.
I agree on the need to define use case scenarios. I for one would like to "fix" the Struts/JSF confusion, and maybe integrate and promote Struts-Faces or a similar implementation, much like we are promoting the use of JSTL-tags instead of the bean/logic taglibs. This, of course, doesn't rule out next generation web apps and special request/resonse types, but we should IMO first and foremost define how much of an evolution or revolution we want. \Anders --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
