Details
-
Wish
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
5.0.7
-
None
-
None
Description
Type coercion automatically coerces null objects of type like Integer and Double to 0.
I don't think that in most cases this is the desired behaviour. null is definitely different from 0 so Tapestry is loosing information in the middle.
My suggestion is that the types in java.lang when null should be coerced to null. The collection type should be coerced to empty collections like they currently are.