All the posts and topics that contain only an error report will be moved here after the error is corrected. This is to ensure that when users view a question in ETS Viewer, the "Discuss" button will not indicate the presence of a discussion that adds no value to the question.
The <taglib> tag comes directly under the web-app element and it is used to specify the mapping between the name that will be used in the JSP pages and the URI where the actual tag library descriptor (.tld file) is located.
You are right. It seems the old 2.4 dtd has it under web-app and in 3.0 it is under jsp-config.
This has now been fixed.
thank you for your feedback!
-Paul.
If you like our products and services, please help us by posting your review here.
1. Make a jar file of all the classes and include *.tld files in META-INF directory inside the jar.
For consistency it should be mentioned that not only META-INF directory, but also its subdirectories (JSP 2.2 specification: JSP.7.3.1 Identifying Tag Library Descriptors):
When deployed inside a JAR file, the tag library descriptor files must be in the META-INF directory, or a subdirectory of it.
"specify the mapping of the name and the TLD file for a tag library."
The taglib element specifies a mapping between taglib-uri and a taglib-location. Why does this correct option states that it is a mapping between name and TLD file? Shouldn't it be changed to say:
"specify the mapping of the uri and the TLD file for a tag library."
<taglib>
<taglib-uri>/mylibrary</taglib-uri> ( You can use 'mylibrary' in the JSP taglib directive : <%@taglib uri="/mylibrary" prefix=="mylib"%> )
<taglib-location>/WEB-INF/tlds/MYLibrary.tld</taglib-location> // This is the location of tld file for the tag library.
</taglib>
If you like our products and services, please help us by posting your review here.
I completely agree with the above post. "uri" is not "name" otherwise the taglib directive would have been <%@ taglib name="" prefix="" %> and deployement descriptor would use <taglib-name> instead of <taglib-uri>.
The correct option should be mapping between uri and TLD.
The correct answer 2. still says, "specify the mapping of the name and the TLD file for a tag library.". I was confused by the name too. If it'd said,"specify the mapping of the uri and the location of TLD file for a tag library.", I'd have gotten it right. As a result, I picked 4. "specify the TLD file location.".
In your explanation:"Note that the mapping information contained within the tld file will always be loaded by the container. The <taglib> tag in web.xml is used to provide any additional taglib-uri mappings. And for those additional mappings, you will need to specify the taglib-location.", which sounds like tld files are looked in first before looking into DD.
But in HFSJ p485, it says,"when the Container begins to build the <uri>-to-TLD map, the Container will look first in your DD to see if you've made any <taglib> entries, and if you have, it'll use those to help construct the map.".