Hi Bill, >Then AddVendorAction takes AddVendorForm as input, and then creates a >DisplayVendorDetailForm in the request context before forwarding to >displayVendor.jsp. Thanks for your feedback.
You're right, but you're doing it by yourself in application code. This is one of the main idea of OzStruts. And I think this task should be done by framework, which makes applicaitn code consistence. In Struts, the framework only makes AddVendorForm available to vendorDetail.jsp. In OzStruts, you don't have to set DisplayVendorDetailForm into request attribute manually. Btw, I don't think it's normal practice in exisiting Struts application development, or I just misunderstood the reality of the Struts development. Page-driven programming is also important to me, because I don't want to see struts-config to maintain the code. To make this concept into code, I don't want to see request.setAttribute() in my application codes. In validation error transition, pre-population is also a key feature of OzStruts. You can say you can do it in each Action calss or some other techique. But I also would like to have consistence way by framework, then prepareRequiredProperties() with transitionContext object is there. I guess it's similar to prepare() method in Shale. Thanks, Tak --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
