This behavior has to do with the "bindMissingValuesAsNull" routine in the DefaultActionBeanPropertyBinder.
I've got a field in the form that corresponds to the base name of the parameter bean (in my example previously, a field named "thing" in addition to fields named "thing.x" and "thing.y". On this particular form submit, however, that form field is disabled on the page and so the parameter does not appear in the HTTP request at all. It seems that Stripes is finding the field name in the "FIELDS_PRESENT" parameter and acting (incorrectly, in my case) on that. How can I tell Stripes not to do that? -- 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
