[ http://mc4j.org/jira/browse/STS-461?page=comments#action_11021 ] Phil Sladen commented on STS-461: ---------------------------------
You really think I'm talking about binding "asdfadf" into an integer! Of course that should cause a validation failure before binding, but that's not the point I'm trying to make. Also, not sure which part of that link is actually relevant to this post. Once an action is called, all properties have been bound. If the form effectively contains 2 updates and I still want the first to succeed even though the 2nd may fail (because of validation failure generated in the action) then the redisplay of the form won't show the first update. In my case, I was having an add record, which for one of the fields allowed the user to create a new record description. Just because the record addition failed for, say, a date reason, it's a little bit off to expect the user to re-enter the new record description field. When the form is redisplayed it's much nicer to have the record description set to the one they just defined and let them re-enter the date. I can see that this is an unusual use-case and perhaps the overhead to the framework of deciding which properties have been updated just isn't worth it. Or more to the point there are more important things to be getting on with. > 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
