You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2011/08/11 20:44:28 UTC
[jira] [Commented] (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
[ https://issues.apache.org/jira/browse/TAP5-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083366#comment-13083366 ]
Hudson commented on TAP5-1535:
------------------------------
Integrated in tapestry-trunk-freestyle #468 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/468/])
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
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1156714
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/transform/InjectContainerWorker.java
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/CoreBehaviorsTests.java
> 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