Ok - for me it's almost ok, but /WEB-INF/mytlds/tld1.tld is not uri, but taglib-location ...
Who can explain me this ?
SCJP5.0, SCWCD5.0, OCEJPAD6, OCPJWSD6
And what if we create taglib with uri "/WEB-INF/mytlds/tld1.tld", put it into file /WEB-INF/mytlds/tld2.tld and in taglib directive we add:
<%@ taglib prefix="mytags" uri="/WEB-INF/mytlds/tld1.tld" %> ?
Which tag will have prefix mytags ? That in file tld1.tld or that in file ltd2.tld but with uri = /WEB-INF/mytlds/tld1.tld ?
SCJP5.0, SCWCD5.0, OCEJPAD6, OCPJWSD6
In tld file we have: <uri>http://abc.com/tld/mytaglib</uri>
and enthruware claim that to use that tag we use in JSP:
<%@ taglib prefix="mytags" uri="/WEB-INF/mytlds/tld1.tld" %>
. so option
is not a right option.b) <%@ taglib prefix="mytags" uri="/WEB-INF/mytlds/tld1.tld" %>
SCJP 1.4, SCWCD 5
If both above fails it seems to try to look for TLD file named like uri.
Yes, I know that Head First says that uri is name and it's not connected in any way with physical location of the file. But enthruware claim that it is, and my tests shows that they are right.
SCJP 1.4, SCWCD 5
I once met a man from Nantucket. He had a tiny ad
New web page for Paul's Rocket Mass Heaters movies
https://coderanch.com/t/785239/web-page-Paul-Rocket-Mass
|