You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2015/10/20 16:19:27 UTC
[jira] [Closed] (TAP5-2487) t:extension-point declaration in
tapestry_*.xsd's have never been correct
[ https://issues.apache.org/jira/browse/TAP5-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Kemnade closed TAP5-2487.
--------------------------------
Resolution: Fixed
Assignee: Jochen Kemnade
Fix Version/s: 5.4
> 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
> Assignee: Jochen Kemnade
> Labels: 54_release_prerequisite
> Fix For: 5.4
>
>
> 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)