tomcat-taglibs-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Neil Zanella <>
Subject Re: Jakarta Taglibs Installation
Date Fri, 04 Jul 2003 21:51:04 GMT

Well, now I am not entirely sure that it is mandatory, because I have
a JSP page such that when I change the WEB-INF/web.xml to include the
following lines (for connecting to a database which is not yet on the


and save the .jsp file without making any modifications to it, I get
the following error, but the error is not caused by a change in the
.jsp file; it's caused by the above lines:

org.apache.jasper.JasperException: This absolute uri 
( cannot be resolved in either web.xml or 
the jar files deployed with this application

This is clearly wrong!!! BTW I have not been able to connect to the data
source yet so I'm not sure yet if that would fix it, but the error is
clearly the wrong error, and is introduced by the above lines.

Why is this happening? (almost would seem like a bug: Tomcat 4.1.24)


On Mon, 30 Jun 2003, Shawn Bayern wrote:

> On Mon, 30 Jun 2003, [gb2312] guo yingshou wrote:
> > If it is *mandatory*,why the web-app.dtd still specifiy an optional
> > taglib element?Just for backward compatibility?
> That's part of it, and it's also necessary for cases where a tag library
> doesn't package its JAR in the format necessary for it to work.  Note that
> it's mandatory for the container to support it; it's not mandatory for a
> taglib author to deploy his or her libraries in this fashion (though it's
> probably a good idea in all cases).

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message