Verify by examining the contents of your jar files. Maybe you are looking for a class that is specified in JSTL 1.1 but no longer exists in JSTL 1.2 while you have clearly downloaded the JSTL 1.2 libraries or something like that.
Joined: Feb 25, 2008
Thank you for your answer. I will try that. But it's a very very very simple example for JSF. Therefore I don't think, thats the reason, but I will examin the jar files.
Joined: Oct 26, 2010
Well after checking javadocs for both JSTL 1.1 and 1.2 I see that your class in question is in fact in both version of the API and so should be in the jar file regardless of which one you have so my original suggestion (which admittedly was just the first thing that came to mind) doesn't seem to hold much validity in your case. Are you using an IDE? Are you packaging in a .war file inside an .ear file or anything or just a standalone .war file? When you say you are 'including' the jars, what exactly do you mean? Putting them in WEB-INF/lib of the .war file? If you are using an ANT script or some IDE function to package your .war, have you examined the contents of the .war you are deploying to make sure it actually included the jar files?