[TAP5-715] TypeCoercer.explain incorrectly reports the plan to coerce from primitive types to wrapper types

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.1.0.5
• Fix Version/s: 5.2.0
• Component/s: tapestry-ioc
• Assignee: Howard Lewis Ship
• Reporter: Lukasz Jazgar
• Created: 21/May/09 12:44
• Updated: 07/Jan/10 00:11
• Resolved: 07/Jan/10 00:11

Description

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?