[TAP5-1383] TypeCoercer should "promote" coercions to primitive types into coercions to the corresponding wrapper type

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.2.4
• Fix Version/s: 5.3
• Component/s: tapestry-ioc
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 22/Dec/10 00:24
• Updated: 04/Jul/11 20:21
• Resolved: 02/Apr/11 00:34

Description

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.