You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/04/02 02:36:19 UTC
[jira] [Closed] (TAP5-1383) TypeCoercer should "promote" coercions
to primitive types into coercions to the corresponding wrapper type
[ https://issues.apache.org/jira/browse/TAP5-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1383.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.3.0
Assignee: Howard M. Lewis Ship
> TypeCoercer should "promote" coercions to primitive types into coercions to the corresponding wrapper type
> ----------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1383
> URL: https://issues.apache.org/jira/browse/TAP5-1383
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.2.4
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.3.0
>
>
> Got bit by this.
> Adding a coercion from Foo.class to boolean.class is accepted, but then passing a Foo as the test parameter of an If causes an implicit type coercion to Boolean (the wrapper class). The Foo-->boolean was ignored in favor of Object-->String, String-->Boolean.
> TypeCoercer should either forbid coercions to primitive types, or record the coercion as coercion to the wrapper type.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira