[
https://issues.apache.org/jira/browse/TAP5-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015291#comment-13015291
]
Peter Rietzler commented on TAP5-995:
-------------------------------------
You are right. I've just added this issue because it feels strange that there
is an exact coercion from the source to the target type but in fact another one
is used. We've solved this problem by checking this case before calling the
actual resolving algorithm.
> 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
