Maybe try and delete the app's folder in the TOMCAT_HOME/webapps, then deploy again. Make sure the correct libraries are contained in the WEB-INF/libs folder then. Other than this...no idea what might be wrong. I'm also using the JSTL implemenation with the two files (you probably got them from here?) and it works for me, although in a slightly older tomcat (6.0.18).
Pat Farrell wrote:No servlet or jsp, but I thought the jstl-1.2.jar was supposed to (required to) be in the WEB-INF/lib
Yes, the JSTL jars go in WEB-INF/lib. But sometimes people copy the JSP and servlet jars from the container to their WEB-INF/lib and that causes no end of hard-to-debug mayhem. It's one of the first things I advises checking for when otherwise inexplicable behavior arises.
Pat Farrell wrote:Tried @bear's one file jstl-1.2.jar and still no joy
OK, that means it's something environmental and not an issue with the JSTL jar file(s).
Is this a brand spanking new Tomcat install?
If so, what I'd do next is to create a minimal alternate web app and see if the JSTL loads correctly without anything else possibly getting in its way. If it loads, then it's likely something in your app, if not, there's likely an issue with the Tomcat install.
Stefan Evans wrote:My guess would be the WEB-INF folder is in the wrong place.
The path was listed as:
Which one of these would be the Tomcat web context root? /sandbox/wayserver/webapi/web/ ?
How have you specified this in Tomcat?
What URL do you use to access your jsp page?
Entirely possible to be wrong. Where is this "specified"?
There is no /sandbox or even ~/sandbox on the Tomcat server, that's cruft from my development machine. All of the specs are supposed to be relative.
Then I would expect to see on Tomcat something like
If you have bundled the application in a WAR, then again, WEB-INF needs to be a top level directory, not packaged under "web"
If it can't find your WEB-INF/lib directory, it won't find the JSTL jar, and thus won't locate the uri for the tag library.