On Fri, Jan 16, 2009 at 4:30 AM, Héctor López <[email protected]> wrote: > I've just done a quick and dirty test, and i'm unable to reproduce it as you > are describing. It would be helpful to see some of your code...
I'll see if I can extract it out; it's not a very complicated action and not a very complicated form. There really are just two "thing.x" and "thing.y" parameters. Looking at the Stripes code, it seems to me pretty clear what's going on. Stripes sorts the *actual* parameters and binds them. It then goes back and looks at the "__fp" parameter to determine what was actually coded into the <stripes:form> on the page. It iterates through that list without checking the finer points, setting each one to null. I understand why setting not-present form parameters to null might be useful in some cases, but I don't see how it's ever a good idea to set "thing" to null *after* it has already set "thing.x" and "thing.y". -- Turtle, turtle, on the ground, Pink and shiny, turn around. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
