Thanks very much for taking the time - I greatly appreciate it. On Shawn Bayern's sage advice, I put the standard.jar in the CLASSPATH and make the URI identical to the value in the c.tld file inside the jar. I don't put the .tld files under my WEB-INF, and I don't have any reference to them inside my web.xml. I let Tomcat sort them out using the JAR that the developers provided. Shawn Bayern gave this advice on the JSTL list a while back, and I've followed it ever since:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg04587.html Both the echo and data source test apps are set up that way, too. I downloaded the JSTL from Jakarta. It's the standard 1.0.3 version. I'm using only the EL tags, not the RT tags. Excellent suggestion. I went into the standard.jar and checked the class name for the <c:redirect url> tag. The tag class is org.apache.taglibs.standard.tag.el.core.RedirectTag, and I can see it in the JAR. I'll turn on more log messages and see what they tell me. Thanks. Here's a "DLL Hell" question for you: where should all those JARs go? I put my JDBC JARs in the TOMCAT_HOME/common/lib directory, as the docs instruct. I've got the JSTL JARs in TWO places: TOMCAT_HOME/common/lib AND in the WEB-INF/lib directory in my WAR file. Could that be it? If I put the JSTL JARs in TOMCAT_HOME/common/lib, I get the benefit of all apps seeing updates at the same time and the harm of breaking if only one of them needs an update. Keeping them close to the app and putting them in the WEB-INF/lib of the WAR file should prevent breakage from new versions, but forcing the effort of changing all those JARs when an update occurs. Which do you recommend? Sorry to be stringing these questions together like this. Please stop me the moment I become an annoyance. Thanks - MOD --- "Shapira, Yoav" <[EMAIL PROTECTED]> wrote: > > Howdy, > > >Yoav Shapiro, I hope you're still out there. > > I'm always out here ;) Sometimes I don't feel > like answering but as I mentioned on taglibs-user, > this is more interesting than most questions on the > list. > > >(1) and (2) deploy and run perfectly. (3) deploys > >without any error messages to the log, but I still > get > >that exception when I invoke the index.jsp: > > OK, so we know your JSTL implementation used by apps > 1 and 2 is fine, and that your tomcat installation > is fine. > The problem has to be in how webapp 3, your app, > configures > JSTL. > > Are the taglib files in the right place? Do the > declarations > in webapp 3's web.xml file match the taglib > locations? > > You're also sure you have the distributed version of > the > core taglib, right? Not some customized version > that may > not have the redirect tag defined? In any case, it > can't > hurt to double-check the core .tld file and make > sure > the redirect tag is defined there. > > >The JSP itself is quite simple: > > > ><%@ page language="java" %> > > > ><%@ taglib prefix="c" > >uri="http://java.sun.com/jstl/core"; %> > > > ><c:redirect url="api-welcome.jsp"/> > > > >It complains about the <c:redirect> tag. > > Yup, line 4 char 0 from the error messages is > that redirect tag. I would also enable more verbose > output from the JSP servlet (defined in > $CATALINA_HOME/conf/web.xml). > > Yoav Shapira > > > > This e-mail, including any attachments, is a > confidential business communication, and may contain > information that is confidential, proprietary and/or > privileged. This e-mail is intended only for the > individual(s) to whom it is addressed, and may not > be saved, copied, printed, disclosed or used by > anyone else. If you are not the(an) intended > recipient, please immediately delete this e-mail > from your computer system and notify the sender. > Thank you. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
