Yep, I think this is likely a 2.0 Rev a clarification. I've updated the
issue report and added a comment. I can see why this is happening because we
never treated a null as a meaningful value in a UIInput before, so it isn't
overwriting the existing value.
-Dan
On Wed, Jan 20, 2010 at 8:49 AM, Matthias Wessendorf <matzew(a)apache.org>wrote:
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen