You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/02/26 20:15:02 UTC

[jira] Commented: (TAP5-36) Only the last of multiple t:parameter components with the same name in the same grid are rendered, without an error message.

    [ https://issues.apache.org/jira/browse/TAP5-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677107#action_12677107 ] 

Howard M. Lewis Ship commented on TAP5-36:
------------------------------------------

Part of this is because component bindings in the @Component annotation are allowed to conflict with attributes in the template (the template attributes are ignored).

> Only the last of multiple t:parameter components with the same name in the same grid are rendered, without an error message.
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-36
>                 URL: https://issues.apache.org/jira/browse/TAP5-36
>             Project: Tapestry 5
>          Issue Type: Bug
>    Affects Versions: 5.0.15
>         Environment: Windows XP SP 2, Jetty Launcher 5.1.12, Maven 2.0.9, Hibernate 3.2.2, Eclipse 3.3.2, FireFox 2.0.0.15, IE7
>            Reporter: Daniel
>            Priority: Minor
>
> If two parameters are specified with the same name inside a grid component (for example) in a tml file, Tapestry seems to ignore the first one and render only the second.
> Can Tapestry throw an exception when there is a conflict between identically named parameter components?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.