I entered a similar question and got no response. I'm not sure why there was no response, maybe no one knows.
The purpose of the JSP page <%@ taglib> URI attribute in my "opinion" is to allow developers to use short convenient names which map to <taglib> uri entries in the web.xml file. The app server should (in my opinion) lookup the vender URI from the TLD file pointed to in the <taglib> location attribute. I suspect this is a bug (when the TLD is required for validation) or I am wrong. If you look in the TLD file of the library you want to use, you will see the URI which you need to use in your <%@ tablib> URI attribute. Note, I found this to only be true for tag libraries which use validation features of the TLD! Not all taglibs require this workaround. For example, the format taglib does but the core does not! Go figuer. Hope this helps. And I hope someone more knowledgeable speaks up! Thanks, Douglas Ross Developer, HTML UI Framework Kronos E-mail: [EMAIL PROTECTED] Voice: (978) 947-4305 Fax: (978) 256-2474 www.kronos.com Smaller, Faster, Sharper, Easier(tm) -----Original Message----- From: Chris Gow [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 03, 2004 8:40 AM To: [EMAIL PROTECTED] Subject: taglib uri Hi: I noticed in the application documentation that distributed with the 1.1 that the URI I am supposed to define in my JSP page is http://java.sun.com/jsp/jstl/core. However, in order to get jstl to work correctly, I had to use http://java.sun.com/jstl/core (note that the jsp part has been removed). I'm a little puzzled. Which is incorrect and why? thanks -- chris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
