[ https://issues.apache.org/jira/browse/TAP5-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965157#comment-14965157 ]
ASF subversion and git services commented on TAP5-2487: ------------------------------------------------------- Commit 5473e9a538faa512f5bd83d58a68697f6ce79565 in tapestry-5's branch refs/heads/master from [~jkemnade] [ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=5473e9a ] TAP5-2487: fix replace and extension-point attribute declarations in XSD > t:extension-point declaration in tapestry_*.xsd's have never been correct > ------------------------------------------------------------------------- > > Key: TAP5-2487 > URL: https://issues.apache.org/jira/browse/TAP5-2487 > Project: Tapestry 5 > Issue Type: Bug > Affects Versions: 5.3, 5.4, 5.2, 5.1 > Reporter: Chris Poulsen > Labels: 54_release_prerequisite > > JetBrains has just improved their tapestry plugin to use the specfied > tapestry_x_x.xsd when indicating errors in .tml files. > <t:extension-point id="<id>"> is flagged with a missing required attribute > name (according to the xsd), however the ExtensionPointToken / > SaxTemplateParser seems to expect an attribute called "id" being specified, > using "name" results in a tapestry exception: > ... > Caused by: org.apache.tapestry5.ioc.internal.util.TapestryException: Element > <extension-point> does not support an attribute named 'name'. The only > allowed attribute name is 'id'. > I guess the easiest fix is to alter the xsd's to match the actual parser code > to prevent breaking existing tapestry applications. > This is a trivial fix and could be a nice thing to have in place before > releasing 5.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)