tomcat-taglibs-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fanguang Meng" <>
Subject Re: org.apache.jasper.JasperException: This absolute uri ( cannot be resolved in either web.xml or the jar files deployed with this application
Date Wed, 04 Aug 2004 13:32:17 GMT


The Tomcat 4.1.24 we got here is a package that was delivered to us and all
sites to keep us similar.  In a way it came from Apache, but the developers
from Landover got it first, made their modifications and configuration and
then delivered to us.

I have to work within our baseline constraints on this one, sorry about

I downloaded the Tomcat 4.1.30 to PC and tried that standard-examples and
works fine.

What do you think? Maybe some configuration of Tomcat didn't work?

We are using java version "1.2.2"
Solaris VM (build Solaris_JDK_1.2.2_10, native threads, sunwjit)
Does this matter?

Thanks very much.

Fanguang Meng

                      Justyna Horwat                                                     
                      <Justyna.Horwat@S        To:       Tag Libraries Users List <>
                      un.COM>                  cc:                                    
                                               Subject:  Re: org.apache.jasper.JasperException:
This absolute uri                     
                      08/03/2004 11:26          ( cannot be
resolved in either web.xml or the jar files 
                      AM                        deployed with this application           
                      Please respond to                                                  
                      "Tag Libraries                                                     
                      Users List"                                                        

Are you running a vanilla install of Tomcat 4.1.24 that you downloaded
from Apache or is it customized/part of a bundle?

What's odd is when I told you to place your jar files in the WEB-INF/lib
directory then the web application classloader will load those classes
and parse TLD's. It overrides the bootstrap, system, common, and shared
classloaders. You shouldn't be getting this error.

You can also make your classes available across all your web
applications using classloaders other than the web application but you
will not get your TLD's parsed.

Here is a document that gives a Tomcat 4.1.x classloading overview:

Check with your sysadmin and ask where they got their Tomcat installation.

Another thing to try is download Tomcat 4.1.30 from Apache yourself and
deploy the samples web application as well as your own application.



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

View raw message