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 2010/01/07 01:12:54 UTC
[jira] Updated: (TAP5-715) TypeCoercer.explain incorrectly reports
the plan to coerce from primitive types to wrapper types
[ https://issues.apache.org/jira/browse/TAP5-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-715:
--------------------------------------
Summary: TypeCoercer.explain incorrectly reports the plan to coerce from primitive types to wrapper types (was: Coercion from primitive types to wrapper classes?)
> TypeCoercer.explain incorrectly reports the plan to coerce from primitive types to wrapper types
> ------------------------------------------------------------------------------------------------
>
> Key: TAP5-715
> URL: https://issues.apache.org/jira/browse/TAP5-715
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.1.0.5
> Reporter: Lukasz Jazgar
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.2.0
>
>
> I checked 2 cases:
> typeCoercer.explain(boolean.class, Boolean.class)
> returns
> Object --> String, String --> Boolean
> typeCoercer.explain(int.class, Integer.class)
> returns
> Number --> Long, Long --> Integer
> Strange.
> Shouldn't TypeCoercer cast directly to wrapper classes?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.