Re: tld files inside jars are not auto discovered
You need to install your tld in /META-INF/. Paths in jar files are case-sensitive. "Aaron Loucks" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] >I can't get TLD auto discovery to work for any custom taglibs i write > when I package them as jars. It works fine for the standard taglibs > (core, fmt, etc..). The tld file is packaged inside the jar as > '/meta-inf/breadcrumbs_1_0.tld', and breadcrumbs-1.0.jar is located in > /WEB-INF/lib. If i put a copy of the tld in the WEB-INF directory and > add a entry for it in web.xml, I'm able to use the tags. I > don't understand why Tomcat (5.0.28) is auto detecting the TLD files > inside the standard taglibs (standard.jar), but it won't autodetect them > in jar files i produce. Any help would be greatly appreciated. > > -Aaron > > test.jsp: > > <%@ page language="java" contentType="text/html; charset=ISO-8859-1" >pageEncoding="ISO-8859-1" %> > > <%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core"; %> > <%@ taglib prefix="bc" > uri="http://projects.cofront.net/tablibs/breadcrumbs"; %> > > > > > > Breadcrumb Test > > > >page1 >page2 >page3 > > > > > > Produces the following error: > > org.apache.jasper.JasperException: The absolute uri: > http://projects.cofront.net/tablibs/breadcrumbs cannot be > resolved in either web.xml or the jar files deployed with this application > > org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:50) > > org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:411) > > org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:118) > > org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:316) > > org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:147) >org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:418) >org.apache.jasper.compiler.Parser.parseDirective(Parser.java:483) >org.apache.jasper.compiler.Parser.parseElements(Parser.java:1539) >org.apache.jasper.compiler.Parser.parse(Parser.java:126) > > org.apache.jasper.compiler.ParserController.doParse(ParserController.java:220) > > org.apache.jasper.compiler.ParserController.parse(ParserController.java:101) >org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:203) >org.apache.jasper.compiler.Compiler.compile(Compiler.java:470) >org.apache.jasper.compiler.Compiler.compile(Compiler.java:451) >org.apache.jasper.compiler.Compiler.compile(Compiler.java:439) > > org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511) > > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295) > > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) >org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) >javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > > *note* _The full stack trace of the root cause is available in the > Apache Tomcat/5.0.28 logs. > > > > _breadcrumbs_1_0.tld: > > > > http://java.sun.com/xml/ns/j2ee"; >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee > http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_0.xsd"; >version="2.0"> > > Breadcrumbs library > Breadcrumbs > 1.1 > bc > http://projects.cofront.net/tablibs/breadcrumbs > >Creates Breadcrumbs. >breadcrumbs >net.cofront.taglibs.breadcrumbs.BreadCrumbsTag >JSP > >Separator string. >separator >yes >true > > >CSS style to be applied to all breadcrumb > links. >style >no >true > > >CSS style class to be applied to all breadcrumb > links. >styleClass >no >true > > > >A Breadcrumb. >breadcrumb >net.cofront.taglibs.breadcrumbs.BreadCrumbTag >JSP > >URL >href >true >false > > > > > > web.xml: > > http://java.sun.com/xml/ns/j2ee"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee > http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"; > version="2.4"> > >ROOT > > >action > > org.apache.struts.action.ActionServlet > >config >/WEB-INF/config/struts-config.xml > >1 > > >@maven.tomcat.generated@ > > >action >*.do > > > > > > > >index.html >index.htm >index.jsp > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tld files inside jars are not auto discovered
I double checked the jar file and the META-INF is in uppercase. Still no luck =/ Bill Barker wrote: You need to install your tld in /META-INF/. Paths in jar files are case-sensitive. "Aaron Loucks" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] I can't get TLD auto discovery to work for any custom taglibs i write when I package them as jars. It works fine for the standard taglibs (core, fmt, etc..). The tld file is packaged inside the jar as '/meta-inf/breadcrumbs_1_0.tld', and breadcrumbs-1.0.jar is located in /WEB-INF/lib. If i put a copy of the tld in the WEB-INF directory and add a entry for it in web.xml, I'm able to use the tags. I don't understand why Tomcat (5.0.28) is auto detecting the TLD files inside the standard taglibs (standard.jar), but it won't autodetect them in jar files i produce. Any help would be greatly appreciated. -Aaron test.jsp: <%@ page language="java" contentType="text/html; charset=ISO-8859-1" pageEncoding="ISO-8859-1" %> <%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core"; %> <%@ taglib prefix="bc" uri="http://projects.cofront.net/tablibs/breadcrumbs"; %> Breadcrumb Test page1 page2 page3 Produces the following error: org.apache.jasper.JasperException: The absolute uri: http://projects.cofront.net/tablibs/breadcrumbs cannot be resolved in either web.xml or the jar files deployed with this application org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:50) org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:411) org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:118) org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:316) org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:147) org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:418) org.apache.jasper.compiler.Parser.parseDirective(Parser.java:483) org.apache.jasper.compiler.Parser.parseElements(Parser.java:1539) org.apache.jasper.compiler.Parser.parse(Parser.java:126) org.apache.jasper.compiler.ParserController.doParse(ParserController.java:220) org.apache.jasper.compiler.ParserController.parse(ParserController.java:101) org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:203) org.apache.jasper.compiler.Compiler.compile(Compiler.java:470) org.apache.jasper.compiler.Compiler.compile(Compiler.java:451) org.apache.jasper.compiler.Compiler.compile(Compiler.java:439) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) *note* _The full stack trace of the root cause is available in the Apache Tomcat/5.0.28 logs. _breadcrumbs_1_0.tld: http://java.sun.com/xml/ns/j2ee"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_0.xsd"; version="2.0"> Breadcrumbs library Breadcrumbs 1.1 bc http://projects.cofront.net/tablibs/breadcrumbs Creates Breadcrumbs. breadcrumbs net.cofront.taglibs.breadcrumbs.BreadCrumbsTag JSP Separator string. separator yes true CSS style to be applied to all breadcrumb links. style no true CSS style class to be applied to all breadcrumb links. styleClass no true A Breadcrumb. breadcrumb net.cofront.taglibs.breadcrumbs.BreadCrumbTag JSP URL href true false web.xml: http://java.sun.com/xml/ns/j2ee"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"; version="2.4"> ROOT action org.apache.struts.action.ActionServlet config /WEB-INF/config/struts-config.xml 1 @maven.tomcat.generated@ action *.do index.html index.htm index.jsp - 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]
Re: tld files inside jars are not auto discovered
Aaron are you able to access http://projects.cofront.net/tablibs/breadcrumbs ? I tried just a minute ago and couldnt access this url M- - Original Message - From: "Aaron Loucks" <[EMAIL PROTECTED]> To: "Tomcat Users List" Sent: Sunday, November 27, 2005 1:47 PM Subject: Re: tld files inside jars are not auto discovered >I double checked the jar file and the META-INF is in uppercase. Still no > luck =/ > > Bill Barker wrote: > >>You need to install your tld in /META-INF/. Paths in jar files are >>case-sensitive. >> >>"Aaron Loucks" <[EMAIL PROTECTED]> wrote in message >>news:[EMAIL PROTECTED] >> >> >>>I can't get TLD auto discovery to work for any custom taglibs i write >>>when I package them as jars. It works fine for the standard taglibs >>>(core, fmt, etc..). The tld file is packaged inside the jar as >>>'/meta-inf/breadcrumbs_1_0.tld', and breadcrumbs-1.0.jar is located in >>>/WEB-INF/lib. If i put a copy of the tld in the WEB-INF directory and >>>add a entry for it in web.xml, I'm able to use the tags. I >>>don't understand why Tomcat (5.0.28) is auto detecting the TLD files >>>inside the standard taglibs (standard.jar), but it won't autodetect them >>>in jar files i produce. Any help would be greatly appreciated. >>> >>>-Aaron >>> >>>test.jsp: >>> >>><%@ page language="java" contentType="text/html; charset=ISO-8859-1" >>> pageEncoding="ISO-8859-1" %> >>> >>><%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core"; %> >>><%@ taglib prefix="bc" >>>uri="http://projects.cofront.net/tablibs/breadcrumbs"; %> >>> >>> >>> >>> >>> >>>Breadcrumb Test >>> >>> >>> >>> page1 >>> page2 >>> page3 >>> >>> >>> >>> >>> >>>Produces the following error: >>> >>>org.apache.jasper.JasperException: The absolute uri: >>>http://projects.cofront.net/tablibs/breadcrumbs cannot be >>>resolved in either web.xml or the jar files deployed with this application >>> >>>org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:50) >>> >>>org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:411) >>> >>>org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:118) >>> >>>org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:316) >>> >>>org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:147) >>> org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:418) >>> org.apache.jasper.compiler.Parser.parseDirective(Parser.java:483) >>> org.apache.jasper.compiler.Parser.parseElements(Parser.java:1539) >>> org.apache.jasper.compiler.Parser.parse(Parser.java:126) >>> >>>org.apache.jasper.compiler.ParserController.doParse(ParserController.java:220) >>> >>>org.apache.jasper.compiler.ParserController.parse(ParserController.java:101) >>> org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:203) >>> org.apache.jasper.compiler.Compiler.compile(Compiler.java:470) >>> org.apache.jasper.compiler.Compiler.compile(Compiler.java:451) >>> org.apache.jasper.compiler.Compiler.compile(Compiler.java:439) >>> >>>org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511) >>> >>>org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295) >>> >>>org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) >>> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) >>> javax.servlet.http.HttpServlet.service(HttpServlet.java:802) >>> >>>*note* _The full stack trace of the root cause is available in the >>>Apache Tomcat/5.0.28 logs. >>> >>> >>> >>>_breadcrumbs_1_0.tld: >>> >>> >>> >>>http://java.sun.com/xml/ns/j2ee"; >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >>> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee >>>http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_0.xsd"; >>> version="2.0"> >>> >>> Breadcrumbs library >>&g
RE: tld files inside jars are not auto discovered
You have a typo. uri="http://projects.cofront.net/tablibs/breadcrumbs"; %> Should read: uri="http://projects.cofront.net/taglibs/breadcrumbs"; %> Note: you typed tablibs instead of taglibs. Subir -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Saturday, November 26, 2005 10:15 PM To: users@tomcat.apache.org Subject: Re: tld files inside jars are not auto discovered You need to install your tld in /META-INF/. Paths in jar files are case-sensitive. "Aaron Loucks" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] >I can't get TLD auto discovery to work for any custom taglibs i write > when I package them as jars. It works fine for the standard taglibs > (core, fmt, etc..). The tld file is packaged inside the jar as > '/meta-inf/breadcrumbs_1_0.tld', and breadcrumbs-1.0.jar is located in > /WEB-INF/lib. If i put a copy of the tld in the WEB-INF directory and > add a entry for it in web.xml, I'm able to use the tags. I > don't understand why Tomcat (5.0.28) is auto detecting the TLD files > inside the standard taglibs (standard.jar), but it won't autodetect them > in jar files i produce. Any help would be greatly appreciated. > > -Aaron > > test.jsp: > > <%@ page language="java" contentType="text/html; charset=ISO-8859-1" >pageEncoding="ISO-8859-1" %> > > <%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core"; %> > <%@ taglib prefix="bc" > uri="http://projects.cofront.net/tablibs/breadcrumbs"; %> > > > > > > Breadcrumb Test > > > >page1 >page2 >page3 > > > > > > Produces the following error: > > org.apache.jasper.JasperException: The absolute uri: > http://projects.cofront.net/tablibs/breadcrumbs cannot be > resolved in either web.xml or the jar files deployed with this application > > org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHand ler.java:50) > > org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java :411) > > org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java :118) > > org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLib raryInfoImpl.java:316) > > org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl. java:147) > org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:418) >org.apache.jasper.compiler.Parser.parseDirective(Parser.java:483) >org.apache.jasper.compiler.Parser.parseElements(Parser.java:1539) >org.apache.jasper.compiler.Parser.parse(Parser.java:126) > > org.apache.jasper.compiler.ParserController.doParse(ParserController.jav a:220) > > org.apache.jasper.compiler.ParserController.parse(ParserController.java: 101) >org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:203) >org.apache.jasper.compiler.Compiler.compile(Compiler.java:470) >org.apache.jasper.compiler.Compiler.compile(Compiler.java:451) >org.apache.jasper.compiler.Compiler.compile(Compiler.java:439) > > org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.ja va:511) > > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja va:295) > > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) >org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) >javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > > *note* _The full stack trace of the root cause is available in the > Apache Tomcat/5.0.28 logs. > > > > _breadcrumbs_1_0.tld: > > > > http://java.sun.com/xml/ns/j2ee"; >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee > http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_0.xsd"; >version="2.0"> > > Breadcrumbs library > Breadcrumbs > 1.1 > bc > http://projects.cofront.net/tablibs/breadcrumbs > >Creates Breadcrumbs. >breadcrumbs > net.cofront.taglibs.breadcrumbs.BreadCrumbsTag >JSP > >Separator string. >separator >yes >true > > >CSS style to be applied to all breadcrumb > links. >style >no >true > > >CSS style class to be applied to all breadcrumb > links. >styleClass >no >true > > > >A Breadcrumb. >breadcrumb > net.cofront.taglibs.breadcrumbs.BreadCrumbTag >JSP > >URL >
Re: tld files inside jars are not auto discovered
What can I say. I just tried copying your TLD, and created two useless classes to implement the Tags, and copied your JSP to webapps/ROOT. It all worked fine. You can try checking that the .tld file ends in a lower-case ".tld", but I don't know what else to suggest. For what it's worth, here a dump of my working jar: $ jar -tf breadcrumb.jar META-INF/ META-INF/MANIFEST.MF META-INF/_breadcrumbs_1_0.tld BreadCrumbsTag.java net/ net/cofront/ net/cofront/taglibs/ net/cofront/taglibs/breadcrumbs/ net/cofront/taglibs/breadcrumbs/BreadCrumbsTag.class net/cofront/taglibs/breadcrumbs/BreadCrumbTag.class BreadCrumbTag.java "Aaron Loucks" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] >I double checked the jar file and the META-INF is in uppercase. Still no >luck =/ > > Bill Barker wrote: > >>You need to install your tld in /META-INF/. Paths in jar files are >>case-sensitive. >> >>"Aaron Loucks" <[EMAIL PROTECTED]> wrote in message >>news:[EMAIL PROTECTED] >> >>>I can't get TLD auto discovery to work for any custom taglibs i write >>>when I package them as jars. It works fine for the standard taglibs >>>(core, fmt, etc..). The tld file is packaged inside the jar as >>>'/meta-inf/breadcrumbs_1_0.tld', and breadcrumbs-1.0.jar is located in >>>/WEB-INF/lib. If i put a copy of the tld in the WEB-INF directory and >>>add a entry for it in web.xml, I'm able to use the tags. I >>>don't understand why Tomcat (5.0.28) is auto detecting the TLD files >>>inside the standard taglibs (standard.jar), but it won't autodetect them >>>in jar files i produce. Any help would be greatly appreciated. >>> >>>-Aaron >>> >>>test.jsp: >>> >>><%@ page language="java" contentType="text/html; charset=ISO-8859-1" >>> pageEncoding="ISO-8859-1" %> >>> >>><%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core"; %> >>><%@ taglib prefix="bc" >>>uri="http://projects.cofront.net/tablibs/breadcrumbs"; %> >>> >>> >>> >>> >>> >>>Breadcrumb Test >>> >>> >>> >>> page1 >>> page2 >>> page3 >>> >>> >>> >>> >>> >>>Produces the following error: >>> >>>org.apache.jasper.JasperException: The absolute uri: >>>http://projects.cofront.net/tablibs/breadcrumbs cannot be >>>resolved in either web.xml or the jar files deployed with this >>>application >>> >>>org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:50) >>> >>>org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:411) >>> >>>org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:118) >>> >>>org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:316) >>> >>>org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:147) >>> >>> org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:418) >>> org.apache.jasper.compiler.Parser.parseDirective(Parser.java:483) >>> org.apache.jasper.compiler.Parser.parseElements(Parser.java:1539) >>> org.apache.jasper.compiler.Parser.parse(Parser.java:126) >>> >>>org.apache.jasper.compiler.ParserController.doParse(ParserController.java:220) >>> >>>org.apache.jasper.compiler.ParserController.parse(ParserController.java:101) >>> org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:203) >>> org.apache.jasper.compiler.Compiler.compile(Compiler.java:470) >>> org.apache.jasper.compiler.Compiler.compile(Compiler.java:451) >>> org.apache.jasper.compiler.Compiler.compile(Compiler.java:439) >>> >>>org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511) >>> >>>org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295) >>> >>>org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) >>> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) >>> javax.servlet.http.HttpServlet.service(HttpServlet.java:802) >>> >>>*note* _The full stack trace of the root cause is available in the >>>Apache Tomcat/5.0.28 logs. >>> >>> >>> >>>_breadcrumbs_1_0.tld: >>> >>> >>> >>>http://java.sun.com/xml/ns/j2ee"; >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >>> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee >>>http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_0.xsd"; >>> version="2.0"> >>> >>> Breadcrumbs library >>> Breadcrumbs >>> 1.1 >>> bc >>> http://projects.cofront.net/tablibs/breadcrumbs >>> >>> Creates Breadcrumbs. >>> breadcrumbs >>> net.cofront.taglibs.breadcrumbs.BreadCrumbsTag >>> JSP >>> >>> Separator string. >>> separator >>> yes >>> true >>> >>> >>> CSS style to be applied to all breadcrumb >>>links. >>> style >>> no >>> true >>> >>> >>> CSS style class to be applied to all breadcrumb >>>links. >>> styleClass >>> no >>> true >>> >>> >>> >>> A Breadcrumb. >>> breadcrumb >>> net.cofront.taglibs.breadcrumbs.BreadCrumbTag >>> JSP >>> >>> URL >>> href >>> true >>>
Re: tld files inside jars are not auto discovered
The typo was in both the jsp and the tld, so it canceled itself out. The issue was with META-INF afterall. Even thought the extracted jar file had the META-INF folder in uppercase, the original (pre-jar) directory was not in uppercase. I'm guessing that the jar/zip format recoginizes the files: /META-INF/manifest.mf and /meta-inf/breadcrumbs_1_0.tld as being located in two different folders, but when extracted in windows, the files are both placed in the same folder and thus my method of checking the case of the folder was invalid. I changed my maven build so that the target path of the tld was META-INF rather than meta-inf and now it works. Subir Sengupta wrote: You have a typo. uri="http://projects.cofront.net/tablibs/breadcrumbs"; %> Should read: uri="http://projects.cofront.net/taglibs/breadcrumbs"; %> Note: you typed tablibs instead of taglibs. Subir -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Saturday, November 26, 2005 10:15 PM To: users@tomcat.apache.org Subject: Re: tld files inside jars are not auto discovered You need to install your tld in /META-INF/. Paths in jar files are case-sensitive. "Aaron Loucks" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] I can't get TLD auto discovery to work for any custom taglibs i write when I package them as jars. It works fine for the standard taglibs (core, fmt, etc..). The tld file is packaged inside the jar as '/meta-inf/breadcrumbs_1_0.tld', and breadcrumbs-1.0.jar is located in /WEB-INF/lib. If i put a copy of the tld in the WEB-INF directory and add a entry for it in web.xml, I'm able to use the tags. I don't understand why Tomcat (5.0.28) is auto detecting the TLD files inside the standard taglibs (standard.jar), but it won't autodetect them in jar files i produce. Any help would be greatly appreciated. -Aaron test.jsp: <%@ page language="java" contentType="text/html; charset=ISO-8859-1" pageEncoding="ISO-8859-1" %> <%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core"; %> <%@ taglib prefix="bc" uri="http://projects.cofront.net/tablibs/breadcrumbs"; %> charset=ISO-8859-1"> Breadcrumb Test page1 page2 page3 Produces the following error: org.apache.jasper.JasperException: The absolute uri: http://projects.cofront.net/tablibs/breadcrumbs cannot be resolved in either web.xml or the jar files deployed with this application org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHand ler.java:50) org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java :411) org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java :118) org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLib raryInfoImpl.java:316) org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl. java:147) org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:418) org.apache.jasper.compiler.Parser.parseDirective(Parser.java:483) org.apache.jasper.compiler.Parser.parseElements(Parser.java:1539) org.apache.jasper.compiler.Parser.parse(Parser.java:126) org.apache.jasper.compiler.ParserController.doParse(ParserController.jav a:220) org.apache.jasper.compiler.ParserController.parse(ParserController.java: 101) org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:203) org.apache.jasper.compiler.Compiler.compile(Compiler.java:470) org.apache.jasper.compiler.Compiler.compile(Compiler.java:451) org.apache.jasper.compiler.Compiler.compile(Compiler.java:439) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.ja va:511) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja va:295) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) *note* _The full stack trace of the root cause is available in the Apache Tomcat/5.0.28 logs. _breadcrumbs_1_0.tld: http://java.sun.com/xml/ns/j2ee"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_0.xsd"; version="2.0"> Breadcrumbs library Breadcrumbs 1.1 bc http://projects.cofront.net/tablibs/breadcrumbs Creates Breadcrumbs. breadcrumbs net.cofront.taglibs.breadcrumbs.BreadCrumbsTag JSP Separator string. separator yes true CSS style to be applied to all breadcrumb links. style no true CSS style cl
