[ http://mc4j.org/jira/browse/STS-461?page=comments#action_11022 ] John Newman commented on STS-461: ---------------------------------
Ah sorry, I completely misunderstood your post .. i was hoping so. =) You are right, that is a rather unusual use case. Why not just run all validation on their input before doing anything? If the input is bad, fix it straight away. If it's good, do N updates. It's hard to say without seeing your logic. > Wrong default for the Population strategy? > ------------------------------------------ > > Key: STS-461 > URL: http://mc4j.org/jira/browse/STS-461 > Project: Stripes > Issue Type: Bug > Components: ActionBean Dispatching > Affects Versions: Release 1.4.3 > Environment: Windows/Linux, Tomcat 5.5.28 > Reporter: Phil Sladen > Assigned To: Tim Fennell > Priority: Minor > > I had an event handler that updates a few action properties from the > submission, but then returns a validation failure. The form is redisplayed, > but with the property values that were submitted to the action, rather than > with the updated values in the action. Shouldn't the default population > strategy be to take values from the actionbean before the page parameters. > The current default appears to assume that pages are designed to submit to > themselves when they should be submitting to an action. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://mc4j.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Stripes-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-development
