[
https://issues.apache.org/jira/browse/TAP5-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship resolved TAP5-995.
---------------------------------------
Resolution: Won't Fix
I do wish I had used an OrderedConfiguration, not a unordered Configuration,
when defining the TypeCoercer. A solution to your problem probably requires an
ordered configuration ... but TypeCoercer is too wired into the IoC container
(and virtually every Tapestry framework or application) to change. Right now
the TypeCoercer sees the two coercions as equal (same number of steps) and
stops when it finds the first one. As this doesn't seem to affect most users
and most coercions, I'm going to table it for the meantime.
> 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
