[
https://issues.apache.org/jira/browse/TAPESTRY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556179#action_12556179
]
Vjeran Marcinko commented on TAPESTRY-2020:
-------------------------------------------
If anyone cares, I strongly agree on this. Null vale is totally meaningful
value which means absence of some value. I use it constantly in my apps to test
whether some optional property has been set or not. I don't see any reason why
number properties would be treated differently.
> java.lang properties should be coerced to null
> ----------------------------------------------
>
> Key: TAPESTRY-2020
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2020
> Project: Tapestry
> Issue Type: Wish
> Components: tapestry-ioc
> Affects Versions: 5.0.7
> Reporter: Hugo Palma
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
