Rahul P Akolkar wrote:
Stu Robertson <[EMAIL PROTECTED]> wrote on 07/10/2005 04:07:29 PM:
jar? The 2.4 specification allows them to be in the jar, at META-INF/
taglib.tld.
It does not need to be called taglib.tld, it just need to end in a .tld
(the standard.jar, for instance, has 5 TLDs on 1.1.x and 8 on 1.0.x, as
this jar contains multiple taglibs). Also, that has been introduced by
Servlet 2.3/JSP 1.2 (and not only Servlet 2.4/JSP 2.0).
I found that WAS 6 has trouble dealing with it elsewhere
Maybe the problem is where you jar is, not where the TLD is on the jar,
as the specification only requires the TLD scanning of jars contained on
the WEB-INF/lib directory of the web application (it might not scan jars
contained in a hsared directory on the server, for instance - see for
more information on this isse)
It
There is a copy in taglibs-<taglib>.jar/META-INF/taglib.tld, which is
where the spec says it should reside if the taglib is deployed in an
archived form. There is another copy sitting outside the jar as
As I said earlier, that's not exactly true - the taglib.tld name was
mandatory only on previous versions of JSP (like 1.2 - I think, but am
not sure). Anyway, as RDC requires JSP 2.0, we should use a better name
like rdc.tld.
consumption, does anyone have more insight into why there are two TLDs in
the example wars?
I'm sorry, but I missed the discussion, so I might be talkign non-sense.
Anyway, I agree with you that the TLDs could be available outside the
JARs/WARs for 'human reading purposes' only. Inside it, we better keep
the TLD on the META-INF (or even META-INF/tlds) directory.
-- Felipe
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
