Sorry for the repeat... I originally sent this before my subscription
was confirmed and didn't catch the replies...

 

I have an interesting situation where I have configured all my common
taglibs (jstl, etc) within Tomcat's conf/web.xml.  We are now
incorporating a custom tag library and added that to the <jsp-config>
entries:

 

    <taglib>

      <taglib-uri>customTagLibs</taglib-uri>

 
<taglib-location>../../../lib/tld/customTagLibs.tld</taglib-location>

    </taglib>

 

For some reason, we cannot get the thing to identify this custom tag
library.  Here is the entry for the core jstl libraries in the exact
same web.xml file:

 

    <taglib>

      <taglib-uri>http://java.sun.com/jstl/core</taglib-uri
<http://java.sun.com/jstl/core%3c/taglib-uri> >

      <taglib-location>../../../lib/tld/c.tld</taglib-location>

    </taglib>

 

The jar file is in the exact same directory as the jstl.jar and
standard.jar.  The TLD is in the exact same directory as the c.tld.  

 

Here is the testing page (because we wanted to reduce testing to the
bare minimum when things stopped working):

 

<%@ page contentType="text/html; charset=iso-8859-1" language="java"
errorPage="/error.jsp"%>

<%@ taglib uri="http://java.sun.com/jstl/core"; prefix="c"%>

<%@ taglib uri="customTagLibs" prefix="jm"%>

 

<c:set var="coreVar" scope="page" value="Core Value Set"/>

<jm:setIf var="testVar" test="${param.p == null}" trueValue="null"
falseValue="${param.p}"scope="page"/>

 

<html>

<body>

<p>Hello from mm/test.jsp</p>

<img src="/images/test.gif"/>

<p>JM Taglib Var Set: ${testVar}</p>

<p>Core Taglib Var Set: ${coreVar}</p>

</body>

</html>

 

Here is the interesting thing.  If I remove just the custom tag lib
entry from tomcat's conf/web.xml and put it in any apps WEB-INF/web.xml,
it works!    That is, all my other "common" tag lib declarations are
still in conf/web.xml, but the custom tag lib declaration is all by
itself within the WEB-INF/web.xml file.  Everything else is exactly in
the same place, under "{catalinahome}/lib"....

 

What is the difference?  What is special about jstl that allows it to
work there, but not our custom lib coded and referenced in virtually
identical way?

 

Also, we tried at least a dozen variations of the URI, all to no avail.
It ONLY works when I configure the custom tag lib within each app's
WEB-INF/web.xml.  

 

Any ideas?

 

 

 

 

 

 

Reply via email to