RE: [OS-webwork] Empty string property now "" instead of null?

[Patrick Lightbody]

Title: RE: [OS-webwork] Empty string property now "" instead of null?

Well, other objects (like int, Long, etc) will get null, but in the case of “” it is actually a valid conversion. Is the request to (in WebWork, not XWork) treat “” as essentially _null_? Anyone have any thoughts on this? I’d especially like to hear from the WebWork 1 guys (Hani? Rickard?)   -Pat   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mathias Berg Sent: Wednesday, December 10, 2003 6:43 AM To: '[EMAIL PROTECTED]' Subject: RE: [OS-webwork] Empty string property now "" instead of null?   I fully agree with ... Mathias :) if "" then null would be preferred to get. But I guess there is something stopping that. or? /Mathias. -----Original Message----- From: BOGAERT Mathias [mailto:[EMAIL PROTECTED]] Sent: den 10 december 2003 13:16 To: [EMAIL PROTECTED] Subject: [OS-webwork] Empty string property now "" instead of null?   Hi, When a form field (single textfield) is not filled, the request param is an empty string, which translates to an empty string array (ParametersInterceptor), but my property setter is called with an empty string. Should't that be null? Cheers, Mathias   ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive?  Does it help you create better code?  SHARE THE LOVE, and help us help YOU!  Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork