I don't think so. I saw the error inside
jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler/TldLocationsCache int
he method processJars. Here is the source:
/**
* Process all the jar files contained in this web application
* WEB-INF/lib directory.
*/
private void processJars(ServletContext ctxt)
throws JasperException
{
Set libSet = ctxt.getResourcePaths("/WEB-INF/lib");
Iterator it = libSet.iterator();
while (it.hasNext()) {
String resourcePath = (String) it.next();
if (resourcePath.endsWith(".jar"))
tldConfigJar(ctxt, resourcePath);
}
}
As you can see, there is no check for libSet being not null. Although, it might be
that in Tomcat 4.1.3, libSet wil be an empty collection.
Regards
Victor
-----Original Message-----
From: Jeff Turner [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 27, 2002 9:13 PM
To: Tomcat Users List
Subject: Re: Tomcat 4.0.4 Performance - PROBLEM
On Wed, Jun 26, 2002 at 05:37:37PM -0400, Victor Popiol wrote:
> Hi all.
>
> I solved my problem. Jasper was dying for not having a lib directory
> under each web app's web-inf. This sounds like a bug in Jasper2.
Thanks for pursuing this! I just hit the same problem, and found your
solution here to work.
Since Jasper2 doesn't show this behaviour with Tomcat 4.1.3, I'd imagine
it is a (fixed) Catalina bug, not a Jasper bug.
--Jeff
> Thasnks
> Victor
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
