Craig McClanahan wrote in <[EMAIL PROTECTED]> >> I think page-driven development frameworks would exacerbate this problem >> unless they clarify with eloquence up-front how to make a clear >> seperation of the POST processing from the page preparation required for >> the next page. >> > >Yep, that is definitely a key point. Here is why Shale's view >controller helps you do that. The key point is this: > > The initialization code for any page (no matter how you got there) > goes in the prepare() method of the corresponding ViewController. > >The only thing you should do in the action method for processing a >request is to perform the necessary business transaction (save a >record to the database or whatever), then return the outcome code used >for navigation. The next page is responsible for taking care of >itself. > >Simple enough? > I agree with Craig. OzStruts does same thing for you with OzPage.prepareRequiredProperties() even on the curent verion of Struts. then codes will be like what Craig mentioned above.
Tak --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
