I can understand empty field contents resulting in null but ignoring a string-indexed property just because its value happens to be empty not only seems bizarre, but its also inconsistent with the way normal properties are treated. Can anyone shed more light on the this 'design decision'. Thanks.
--- On Tue, 31/3/09, Héctor López <[email protected]> wrote: From: Héctor López <[email protected]> Subject: Re: [Stripes-users] Mapped property ignored if value is empty?? To: "'Stripes Users List'" <[email protected]> Date: Tuesday, 31 March, 2009, 11:17 AM Didn’t reply because that’s a design decision. Stripes treats nulls and blank strings the same way, and I find it very natural. Why do you need to put a blank on a map? Just to know that the user inserted a concrete param name? You have other options, eg. as you are dynamically inserting text inputs, add a hidden with the param name… De: Phil Sladen [mailto:[email protected]] Enviado el: martes, 31 de marzo de 2009 11:10 Para: Stripes Users List Asunto: Re: [Stripes-users] Mapped property ignored if value is empty?? Ok, this seems like a genuine issue to me. Unless someone can put me right about this I will raise it in JIRA, if I can remember how to do that. Thanks. -----Inline Attachment Follows----- ------------------------------------------------------------------------------ -----Inline Attachment Follows----- _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
------------------------------------------------------------------------------
_______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
