On Thu, Jan 15, 2009 at 9:25 PM, Ben Gunter <[email protected]> wrote: > Stripes will call getThing() when binding thing.x and if it returns null, > only then will it call setThing() with a newly created object. It would then > call getThing() again for thing.y and if it still returns null then it would > call setThing() again. That, of course, isn't what should be happening but > the problem would be in your ActionBean, not in Stripes.
That is not what's happening - I'm able to work around the problem by having my setter routine only set the "thing" property if it's null. I can confirm that it's being called when it's non-null via debug statements. > Another possibility is if there are two request parameters named "thing." > Then the setter would be called twice. You might want to use Firebug or > something to see exactly what you're sending to the server. Via TamperData I confirm that I'm just setting the two sub-properties. -- 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
