Am I missing something or is everybody saying the same thing. What struts needs is a view controller mechanism. The only difference is the specifics of the mechanism. JSF v. a struts specific mechanism (OzStruts) or the adaptation of something else.
What I don't understand is what people have against JSF, it looks like comprehensive solution and it provides an opportunity to leverage off non-struts developments. And, as far as being a competitor to struts, it's as much a competitor as JSP and servlets in general are. Struts strength is as the C in MVC and JSF's strength is as a V component. They both have strong support and it makes sense for them to work together. I can't see why the aims of OzStruts can't be achieved through implementing JSF and without having to start from scratch. The other advantage is with the growth of support for JSF new view components become available to struts applications. Zoran > Joe Germuska wrote in <[EMAIL PROTECTED]> >> am finding that a limitation. I would like a clean facility for >> prepopulating forms from system data which interoperates with the >> existing mechanism for prepopulating forms when validation fails and >> the user must try again. I would also like a clean mechanism for >> doing certain kinds of page preparation based on the destination page >> rather than the processing action. I feel that this cleans things up > I leave JSF discussion to experts. > But what Joe would like is exactly OzStruts features on current Struts. > Each OzPage must have prepareRequiredProperties method. > This method in destinaiton OzPage instance will be called > right before Struts dispatchs the JSP page, including validation error > transition. > > The example code with validation is in OzStruts sample applicatin in the > distribution. > Tak --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
