figured it out; for the record, i'll answer my own question:

simply removing the taglib lines from web.xml entirely and referencing them
directly from jsp's solved the problem. 


-----Original Message-----
From: John McGrath [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 03, 2005 12:28 PM
To: struts-user@jakarta.apache.org
Subject: trouble referencing struts taglibs: TldLocationsCache?


Hi All,
 
I'm migrating an application from WebLogic 6.1 to Tomcat 5.0, and having a
problem getting Tomcat to process taglibs correctly. The *.tld files are in
WEB-INF, and web.xml is set up the same as in struts-examples, and the same
as we've been using successfully in WebLogic:
 
<taglib>
<taglib-uri>/tags/struts-bean</taglib-uri>
<taglib-location>/WEB-INF/struts-bean.tld</taglib-location>
</taglib>
 
When I reference a taglib in the standard way:
<%@ taglib uri="/tags/struts-bean" prefix="bean" %>

The page fails, and this exception shows up in the logs:

2005-02-03 12:01:38 ApplicationDispatcher[/mcg_cms] Servlet.service() for
servlet jsp threw exception
org.apache.jasper.JasperException: Unable to initialize TldLocationsCache:
null  at
org.apache.jasper.compiler.TldLocationsCache.init(TldLocationsCache.java:249
)
 at
org.apache.jasper.compiler.TldLocationsCache.getLocation(TldLocationsCache.j
ava:220)
 at
org.apache.jasper.JspCompilationContext.getTldLocation(JspCompilationContext
.java:475)
 at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:417)
 at org.apache.jasper.compiler.Parser.parseDirective(Parser.java:483)
 at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1539)...
(etc.)

It feels like I'm overlooking something small and stupid, but I've been
banging my head against this for two days, and it's giving me a headache.
Any help gratefully appreciated.
 
John


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to