Stu Robertson <[EMAIL PROTECTED]> wrote on 07/10/2005 04:07:29 PM: <snip/> > One question though. Why is the tld included outside of the taglib > jar? The 2.4 specification allows them to be in the jar, at META-INF/ > taglib.tld. I found that WAS 6 has trouble dealing with it elsewhere > if the tag classes and tagx files are in a jar. For my build I've > moved it to the jar itself, which solves the issue. <snap/>
Put simply, that is how the taglibs build has it set up. <reiterate> 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 <taglib>-examples.war/WEB-INF/taglibs-<taglib>.tld, which is where the spec says it should reside if the taglib is deployed in an unarchived form. </reiterate> Removing the copy in WEB-INF/ might indeed be necessary for certain containers if the taglib is deployed using an archived form. Apart from the fact that the TLD outside the jar makes for easier human/dev consumption, does anyone have more insight into why there are two TLDs in the example wars? -Rahul
