Thanks for your reply. You were right, that's 4.1.24. I did remove those <taglib> from web.xml and also c.tld from WEB-INF/ and did not work either.
I just put a very simple code there,like this <[EMAIL PROTECTED] contentType="text/html"%> <%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %> <html> <body> <c:set var="xx" value="23"/> <c:out value="${xx}"/> </body> </html> Same problem. Do you think there is some setting which is not right. I check the log file, 2004-08-02 08:58:45 WebappLoader[/DPC]: Deploying class repositories to work directory /data1/OPS/COTS/tomcat-4 .1.24_datapool/work/Standalone/localhost/DPC 2004-08-02 08:58:45 WebappLoader[/DPC]: Deploy class files /WEB-INF/classes to /data1/OPS/COTS/tomcat-4.1.24_da tapool/webapps/DPC/WEB-INF/classes 2004-08-02 08:58:45 WebappLoader[/DPC]: Deploy JAR /WEB-INF/lib/datapool.jar to /data1/OPS/COTS/tomcat-4.1.24_d atapool/webapps/DPC/WEB-INF/lib/datapool.jar 2004-08-02 08:58:45 WebappLoader[/DPC]: Deploy JAR /WEB-INF/lib/jconn2.jar to /data1/OPS/COTS/tomcat-4.1.24_dat apool/webapps/DPC/WEB-INF/lib/jconn2.jar 2004-08-02 08:58:45 WebappLoader[/DPC]: Deploy JAR /WEB-INF/lib/jstl.jar to /data1/OPS/COTS/tomcat-4.1.24_datap ool/webapps/DPC/WEB-INF/lib/jstl.jar 2004-08-02 08:58:45 WebappLoader[/DPC]: Deploy JAR /WEB-INF/lib/listeners.jar to /data1/OPS/COTS/tomcat-4.1.24_ datapool/webapps/DPC/WEB-INF/lib/listeners.jar 2004-08-02 08:58:45 WebappLoader[/DPC]: Deploy JAR /WEB-INF/lib/standard.jar to /data1/OPS/COTS/tomcat-4.1.24_d atapool/webapps/DPC/WEB-INF/lib/standard.jar It did pick up standard.jar and jstl.jar. The following is the error: org.apache.jasper.JasperException: This absolute uri (http://java.sun.com/jstl/core) cannot be resolved in either web.xml or the jar files deployed with this application at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:105) at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:430) at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:154) at org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:159) at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:354) at org.apache.jasper.compiler.Parser.parseDirective(Parser.java:381) at org.apache.jasper.compiler.Parser.parseElements(Parser.java:795) at org.apache.jasper.compiler.Parser.parse(Parser.java:122) at org.apache.jasper.compiler.ParserController.parse(ParserController.java:199) at org.apache.jasper.compiler.ParserController.parse(ParserController.java:153) at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:227) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:369) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:473) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:190) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2407) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:466) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:585) at java.lang.Thread.run(Thread.java:536) Thanks very much. Fanguang Meng Justyna Horwat <[EMAIL PROTECTED] To: Tag Libraries Users List <[EMAIL PROTECTED]> un.COM> cc: Subject: Re: org.apache.jasper.JasperException: This absolute uri 08/02/2004 04:06 (http://java.sun.com/jstl/core) cannot be resolved in either web.xml or the jar files PM deployed with this application Please respond to "Tag Libraries Users List" Tomcat 4.x does not have a 4.2.24 release. Perhaps you meant 4.1.24? Anyways the latest 4.x release is 4.1.30. With Tomcat 4.x you don't need to manually specify the tld's in your deployment descriptor if they are bundled in an included jar file. They should be loaded automatically from the standard.jar file where they are included in the META-INF directory. This jar file should be placed in your web application's WEB-INF/lib directory. Not sure why you are getting this error but I recommend letting the container parse the TLD's that are bundled in the standard.jar file and avoid specifying them manually. This way you have less to worry about and can avoid possible typos in your deployment descriptor and having to make sure your TLD's are in the right place. Also, there is a JSTL examples war file in your JSTL bundle. I recommend deploying that war file in your container and trying out the examples and making sure they work. Thanks, Justyna --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]