On 7/8/05, Access Denied <[EMAIL PROTECTED]> wrote: > It seems like the Web Flow subproject of spring is pretty cool, > especially for the age-old problem of the <back> button. > > buddy
Buddy, last time I checked, the best Spring Web Flow could do about Back button is to inform you that you broke the flow by submitting stale page. It did not prevent you from going back and seeing that stale page. Struts Dialogs has WizardAction (not advertised yet, cause I have not written good docs on it), which makes things much easier on user and less error-prone: http://www.superinterface.com/strutsdialog/wizardaction.do (you are not signing up for anything, this is just a demo). What you get: * Wizard state is stored completely on server, no hidden fields. * Wizard state always depends on domain model state. * Wizard view is always synchronized with wizard state. * Wizard state is an object, and contains model data or refers to it. * Wizard transition is an object, and can validate itself, taking into account domain model standing. * Back, Forward and Refresh buttons are safe to use. * Error messages are not lost on page refresh. * A wizard can be reconfigured in runtime. * Wizard rules are defined completely in Java, no XML configuration files, no server-side Javascript. * Wizard rules and domain model integration can be tested using base JDK classes only, without user interaction. * Can be used as a component. You can also check this one: http://www.superinterface.com/wizard/signupWizard.do It combines both signup wizard and login control in one easy to use component. I need some time to clean things up. Also, I decided that the simplest way to pursue people to use your stuff is to give them something that they can use in their projects right away. So, I am going to redesign my samples, making a real drop-right-in-the-page components out of them. Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
