https://issues.apache.org/bugzilla/show_bug.cgi?id=43285
Nils Eckert <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
Status|RESOLVED |REOPENED
Resolution|FIXED |
--- Comment #9 from Nils Eckert <[EMAIL PROTECTED]> 2008-05-14 14:03:33 PST ---
As far as this fix changes the behavior in a significant way it is a major
change that will cause a lot of trouble.
With this fix it is not possible to deal with 'optional' number fields. We
don't no whether the user entered the value 0L or 'nothing'. All of our
SearchForms where we add restrictions for not-null fields are not working any
more. To use bindings for such a simple thing is as nonpractical as using
String for number fields.
You are right that your fix follows the JSP 2.1 specification. But even Sun's
reference implementation allows null-values.
To enable Tomcat < 6.0.15 and JSF 1.2 Users to update to Tomcat > 6.0.16 I
would recommend to make this behavoir configurable (e.g. with an context-param)
or follow the RI and allow null-values.
I will provided an other patch that solves Bernhards problem but is aware of
null values. It assigns the value without coercion if it is assignable and uses
coerceToType instead.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
