This content has been marked as final. Show 5 replies
Your classpath is dirty. You have duplicate EL JAR files of different versions around. Clean up your classpath.
Thanks for your reply.
However this doesn´t help i´m afraid. Now i just got the el-api.jar and el-ri.jar remaining in my classpath. Still, the same error message appear when running my application.
Is there any other files or settings that could be a problem?
You shouldn't have any appserver specific libraries in WEB-INF/lib (covered by the webapp's default classpath). Further on the appserver/lib (covered by the appserver's default classpath) should only contain appserver specific libraries and at highest 3rd party libraries which are going to be shared among all webapps. Finally you should NOT have added or modified anything in the jdk/lib (covered by the runtime's default classpath).
So in case of a default and unmodified environment everything should just work flawlessly. In your specific case it seems that you've unnecessarily added/copied appserver specific libraries in the WEB-INF/lib or that you have duplicated EL libraries from (another) appserver in the appserver/lib or maybe -more worse- in the jdk/lib.
This sounds like a migration issue that could be resolved looking over this information .
I looked into this a bit now and it states that if your app already uses EL then yo don´t need to change anything. It is clear that my app uses ValueBinding and MethodBinding and it clearly states that this classes remains in JSF 1.2, so it shouldn´t be a problem. Do you have any directions for med to check?