You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Peter Rietzler (JIRA)" <ji...@apache.org> on 2010/01/28 18:39:34 UTC

[jira] Created: (TAP5-995) First coercion assignable to target type is used instead of most specific target type coercion

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.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (TAP5-995) First coercion assignable to target type is used instead of most specific target type coercion

Posted by "Peter Rietzler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Rietzler updated TAP5-995:
--------------------------------

    Attachment: TypeCoercerImplTest.java

> 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.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (TAP5-995) First coercion assignable to target type is used instead of most specific target type coercion

Posted by "Peter Rietzler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Rietzler updated TAP5-995:
--------------------------------

    Attachment: TypeCoercerImplTest.java

> 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.
-
You can reply to this email to add a comment to the issue online.