<snip> > The other thing I would add is strong debuggability. Is it true that Tapestry's web > debugging is the best of the current crop of web application frameworks?
"Line precise error messages" - are very useful. This however, is not as easy with a JSP engine, given the nature of JSP (template -> source -> compile -> class). Tapestry has the benefit of using it's own html template parser. This provides greater flexibility in terms of "knowing" where something goes wrong. Struts could improve it's configuration error messages. Perhaps someone could write a utility for describing a JspException. Those can be confusing. lots of nested, stacks. But I'm afraid, as long as JSP is the "view", error messages will always lack that of Tapestry. - Mike > > > > > -- > > > > Personally, I believe the original Struts scenario is sound, which is why it has > > lasted so > > long. > > > > (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. > > > > We just need to identify what improvements we need to make at each step, and any > > additional > > steps we'd like to add. > > > > It might be interesting to expand this quick list into a formal set of use-case > > scenarios. If > > you have UML Distilled, Fowler mentions scenarios at the opening of Chapter 3. > > > > -Ted. > > > > > > > > --------------------------------------------------------------------- To > > unsubscribe, e-mail: > > [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] > > > > > >
