If you're using JSF 1.2, then ensure that you're using Tomcat 5.5 and that your web. Xml is declared as Servlet 2.4 (and thus not as 2.3 or older with some old fashioned DOCTYPE )? Xml version="1.0" encoding="UTF-8"?
> But if you're using JSF 2.0, then you need Tomcat 6.0 or newer with Servlet 2. 5 declared web.xml.
If you're using JSF 1.2, then ensure that you're using Tomcat 5.5 and that your web. Xml is declared as Servlet 2.4 (and thus not as 2.3 or older with some old fashioned DOCTYPE). Expression Language (EL) was introduced in JSP 2.0 which is part of Servlet 2.4.The exception indicates that it's declared as Servlet 2.3 or older.
If you're using JSF 1.1, then you should be able to run it on Tomcat 5.0 with a Servlet 2. 3 declared web. Xml (you only need to downgrade JSF 1.2 to JSF 1.1).
But if you're using JSF 2.0, then you need Tomcat 6.0 or newer with Servlet 2. 5 declared web.xml.
Thanks for the valuable inputs but I think I have got the versions correct (by chance :)). My tomcat version is Jan 297, JSF 1.2.04 (INFO: Initializing Sun's JavaServer Faces implementation (1. 2_04-b10-p01) for context 'null') and have this in my web-xml : .
Please tell me what could be wrong? – Mustafa Jan 29 at 16:37 Any chance that the webapp's classpath (/WEB-INF/lib, JRE/lib, JRE/lib/ext and so on) is polluted with old-versioned servletcontainer-specific libraries like jsp-api. Jar and so on which should be left untouched in servletcontainer's own classpath?
– BalusC Jan 29 at 16:56 I have servlet-api and jsp-api in common/lib of tomcat and jstl in my application lib. Changing all that to servlet-api-2.5-6.1.5, jsp-api-2.1-6.0.2 and jstl-1.2 causes my server to never come up :(. Please suggest.
– Mustafa Jan 29 at 17:44 Oh, you should actually never touch the servletcontainer's own libraries! Whenever you want to do that, then you should in fact be upgrading the whole servletcontainer (e.g. Tomcat 5.5 to 6.0). But that's not needed since JSF 1.2 is supposed to run without issues on Tomcat 5.5. I was just asking whenever you have some servletcontainer specific libraries at places they don't belong.
If there are some and they are of a different version, then that would explain the exception you're facing and the solution would be to remove them. – BalusC Jan 29 at 19:17 You need to investigate if the folders /WEB-INF/lib, JRE/lib, JRE/lib/ext do not contain any servletcontainer specific libraries such as jsp-api. Jar, el-api.
Jar, servlet-api. Jar, etc..etc.. Exactly the ones which you already see in Tomcat/common/lib. You should not have duplicates of them elsewhere in the classpath.
I suggest to undo everything and start clean and then do not do "I put a few missing jars", but just report the problem you're facing. Probably you added the wrong JARs or probably it needs to be solved entirely differently. – BalusC Jan 29 at 19:48.
If you're using JSF 1.2, then ensure that you're using Tomcat 5.5 and that your web. Xml is declared as Servlet 2.4 (and thus not as 2.3 or older with some old fashioned DOCTYPE). Expression Language (EL) was introduced in JSP 2.0 which is part of Servlet 2.4. The exception indicates that it's declared as Servlet 2.3 or older.
If you're using JSF 1.1, then you should be able to run it on Tomcat 5.0 with a Servlet 2. Xml (you only need to downgrade JSF 1.2 to JSF 1.1). But if you're using JSF 2.0, then you need Tomcat 6.0 or newer with Servlet 2.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.