We develop using tomcat 3.2.1 and then deploy to Websphere, and we only see this behavior on websphere (Websphere 4.0). We can initialize all the values to "", but I am curious why the two are acting differently.
Thanks for the help, dave dandeneau -----Original Message----- From: Olivier Dinocourt [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 12, 2002 10:43 AM To: Struts Users Mailing List Subject: Re: URGENT: Null Strings in Websphere I might be wrong, but it seems to me that this standard Java behavior.... When your String is null and you try to print it, it displays the String value "null". A workaround might be to force all empty Strings to be "" instead of null... ----- Original Message ----- From: "Dave J Dandeneau" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Tuesday, February 12, 2002 4:38 PM Subject: URGENT: Null Strings in Websphere Whenever we have a String value in our forms, and the value is not set (""), it is getting sent back to the jsp as "null". By "null" I mean the actual string, and not an empty object. This is making validation of these fields fail. Has anyone seen this and found a work around. Thanks, Dave Dandeneau -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
