[
https://issues.apache.org/jira/browse/TAP5-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129143#comment-13129143
]
Hudson commented on TAP5-1329:
------------------------------
Integrated in tapestry-trunk-freestyle #578 (See
[https://builds.apache.org/job/tapestry-trunk-freestyle/578/])
TAP5-1329: Tapestry allows a template to define the same extension-point id
twice, which causes difficult to understand duplicate component id exceptions
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1185348
Files :
*
/tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/SaxTemplateParser.java
*
/tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/internal/services/TemplateParserImplTest.java
*
/tapestry/tapestry5/trunk/tapestry-core/src/test/resources/org/apache/tapestry5/internal/services/dupe_extension_point_id.tml
> Tapestry allows a template to define the same extension-point id twice, which
> causes difficult to understand duplicate component id exceptions
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1329
> URL: https://issues.apache.org/jira/browse/TAP5-1329
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.2
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.3
>
>
> Probably dates back to 5.1.
> If the parent template looks like:
> <t:extension-point id="foo"/> ... <t:extension-point id="foo"/> ...
> and the child template extends:
> <t:replace id="foo"> <t:form t:id="myForm"> ... </t:replace>
> then the exception is that myForm is a duplicate embedded component id.
> Effectively, Tapestry has "pasted" the <t:form ...> into two places of the
> parent template.
> Tapestry should have thrown an exception when parsing the parent template.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
