Summary: | Taglibs Example (1.0.2) is Missing URI in a TLD | ||
---|---|---|---|
Product: | Taglibs | Reporter: | Tony LaPaso <tony> |
Component: | Standard Taglib | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All |
Description
Tony LaPaso
2002-12-09 04:57:30 UTC
Added <uri> definition in WEB-INF/jstl-examples.tld for /jstl-examples-taglib. However, please note that that the problem reported will still persist with tomcat 4.x because of bug 14200. Hans Bergsten is working with the JSP expert group to resolve this issue. Unfortunately, TLD mapping is often source of great confusion. For JSP 1.2, the simplest model is the following: When creating a taglib: - define the <uri> element in the TLD - jar the taglib with the TLD in it Then all a client webapp has to do is - drop the taglib jar file into WEB-INF/lib of the webapp - use the uri defined for the taglib in the <taglib> directive With that model, no modification of the webapp's deployment descriptor (web.xml) is required. I've therefore modified web.xml to remove all the mappings for the JSTL TLDs since they are not necessary, and simply adds to the confusion. The mapping for jstl-examples has been left in there for now because of bug 14200. [One could argue that the taglib defined in the examples webapp should also be built as a jar file. This should definitely be the case if that taglib was to be reused outside of the examples web-app. But since this is not the case, we'll leave it as is (otherwise we'd have to create another directory in standard, examples-taglib, that would specifically host the code for the examples taglib...)] |