5 Replies Latest reply on Aug 4, 2009 1:34 PM by 843844

Property Editor not registered with the PropertyEditorManager

843844 Jul 23, 2009 9:03 AM

I´m trying to integrate a fully working jsf 1.1 application into JBoss 4.2.2 which uses jsf 1.2 which isn´t that compatible at all.
I just have one implementation of the jsf-libs and not any in the application war.

"ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[samigo].[jsp]] Servlet.service() for servlet jsp threw exception
org.apache.jasper.JasperException: Unable to convert string "#{authorFrontDoorMessages.auth_front_door}" to class "javax.el.ValueExpression" for attribute "value": Property Editor not registered with the PropertyEditorManager".

And yes, i have been searching a lot on google and read a lot of the article and forum threads but i haven´t been able to solve this.
I have been struggling with this problem more than a week now, so please give me a tip on what the problem might be.

Any idea?

1. Re: Property Editor not registered with the PropertyEditorManager

843844 Jul 23, 2009 11:22 AM (in response to 843844)

Your classpath is dirty. You have duplicate EL JAR files of different versions around. Clean up your classpath.
Like Show 0 Likes(0)

Actions
2. Re: Property Editor not registered with the PropertyEditorManager

843844 Jul 23, 2009 1:01 PM (in response to 843844)

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?
Like Show 0 Likes(0)

Actions
3. Re: Property Editor not registered with the PropertyEditorManager

843844 Jul 23, 2009 1:06 PM (in response to 843844)

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.
Like Show 0 Likes(0)

Actions
4. Re: Property Editor not registered with the PropertyEditorManager

802577 Jul 23, 2009 3:15 PM (in response to 843844)

This sounds like a migration issue that could be resolved looking over this information [1].

[1] [http://java.sun.com/javaee/javaserverfaces/docs/ReleaseNotes.html#migrating]
Like Show 0 Likes(0)

Actions
5. Re: Property Editor not registered with the PropertyEditorManager

843844 Aug 4, 2009 1:34 PM (in response to 802577)

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?
Like Show 0 Likes(0)

Actions

Go to original post