You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/04/01 02:02:06 UTC
[jira] [Commented] (TAP5-995) First coercion assignable to target
type is used instead of most specific target type coercion
[ https://issues.apache.org/jira/browse/TAP5-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014314#comment-13014314 ]
Howard M. Lewis Ship commented on TAP5-995:
-------------------------------------------
This is a tricky one to deal with. You need a way to measure "distance" and a good definition for "closest".
> First coercion assignable to target type is used instead of most specific target type coercion
> ----------------------------------------------------------------------------------------------
>
> Key: TAP5-995
> URL: https://issues.apache.org/jira/browse/TAP5-995
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.1.0.5
> Reporter: Peter Rietzler
> Attachments: TypeCoercerImplTest.java
>
>
> TypeCoercerImpl uses the first assignable coercion instead of the most specific target type coercion.
> Coercion depends on order of contribution (altough contribution is not ordered).
> See attached unit test.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira