tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-1535) When there's a type mismatch between a container component at the field with @InjectComponent, the type of the containing component should be part of the exception message
Date Thu, 11 Aug 2011 18:24:28 GMT

     [ https://issues.apache.org/jira/browse/TAP5-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship closed TAP5-1535.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.3
         Assignee: Howard M. Lewis Ship

> When there's a type mismatch between a container component at the field with @InjectComponent,
the type of the containing component should be part of the exception message
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1535
>                 URL: https://issues.apache.org/jira/browse/TAP5-1535
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.2.5
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.3
>
>
> Currently, the name of the field with @InjectComponent is identified, as is the type
of that field, but it would make it easier to debug what's gone wrong if the type of the container
component was also in the message, as that's not always obvious from the container's component
id.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message