Mike McNally <emmecin...@...> writes: > > My solution to this is completely different - I subclassed the > parameter binder so that the "missing -> null" work can be shut off on > a bean by bean (event by event) basis via an annotation.
I am getting around this by creating properties in the ActionBean form <s:select> to bind to. There is quite a bit of copy to and from, but not enough to bother me yet. You solution looks very appealing. Can you share your code? This seems to be a common gotcha. I think there should be in a Wiki/FAQ for it. Thanks, Yee > > On Tue, Jun 23, 2009 at 8:40 AM, Lionel<lio...@...> wrote: > > "disabled" on the select tag generates a disabled=true on the html select > > tag, which behaviour is not to send any value. > > Either use readonly attribute or add a hidden value. > > > > Lionel > > > > "CN Yee" <yeechut-re5jqeeqqe8avxtiumw...@...> a écrit > dans le > > message de news: > > 856f41ce0906222324u2336beebi421c2f8a138ab...@... > > Hi, > > > > I have a <stripes:select disabled="true"> tag. > > I just discovered that the disabled="true" is setting null to my actionBean > > object. > > > > Is that the intended behavior? Is there a way to disable it? > > > > Many thanks > > Yee > > > > ------------------------------------------------------------------------------ _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
