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] [Created] (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 Mon, 30 May 2011 19:19:47 GMT
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.2.5, 5.3.0
            Reporter: Howard M. Lewis Ship


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