If you check your GET that is sent via HTTP, you will notice that fields that
are empty are not actually sent over - meaning that the setParameter doesn't
know that it has been set to empty. The only thing it could do is iterate over
the properties setting them to null (string) or something else - but that is as
messy as the solution.
Pascal Houde wrote:
> I don't understand either why it was done like that. Even if the parameter
> is empty it should try to set the property to which .valueOf(String) is
> successful. So properties accepting a B/boolean or String(of course) or
> C/char should be set by the jsp:setProperty action. "Setter" method
> accepting an int would be left unchanged.
>
> Can somebody clears out why it hasn't been done like that. I don't see why
> empty parameters can't be used to set an object property.
--
Richard Vowles, Senior Systems Engineer,
Inprise New Zealand
MAIL: [EMAIL PROTECTED], [EMAIL PROTECTED]
HTTP: http://www.esperanto.org.nz
[my messages contain my own opinions, not those of my employer]
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
For JSP FAQ, http://www.esperanto.org.nz/jsp/jspfaq.html
