Bug 55788 - TagPlugins should key on tag QName rather than implementation class
Summary: TagPlugins should key on tag QName rather than implementation class
Status: NEW
Alias: None
Product: Tomcat 8
Classification: Unclassified
Component: Jasper (show other bugs)
Version: 8.0.x-trunk
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ----
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-16 23:37 UTC by Jeremy Boynes
Modified: 2013-11-16 23:37 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeremy Boynes 2013-11-16 23:37:38 UTC
Tag plugins key off a tag's implementation class, for example:
  <tag-plugin>
    <tag-class>org.apache.taglibs.standard.tag.rt.core.IfTag</tag-class>
    <plugin-class>org.apache.jasper.tagplugins.jstl.core.If</plugin-class>
  </tag-plugin>

This is fragile, for example, if the class name changes or if multiple tags happen to use the same class name. It also means the plugin will not recognize alternate implementations of the same tag, and cannot be used to adapt tagfiles.

Instead, the plugin should key off the tag's fully qualified name (TLD URI + name) such as {http://java.sun.com/jsp/jstl/core, if} for the JSTL <c:if> tag above.