Home/ Questions/Q 7167921
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T14:40:30+00:00

When I access a JPA managed date value from JSF, it comes back with

  • 0

When I access a JPA managed date value from JSF, it comes back with an javax.faces.component.UdateModelException saying

'Cannot convert 01.01.10 00:00 of type class java.util.Date to class org.apache.openjpa.util.java$util$Date$proxy

Using a JPA-managed date value (which means it is proxied) works fine when it is used directly from the EL likes this: 

'<h:outputLabel value="MyDateValue" for="input"/> 
'<h:inputText id="inputDate" value="#{bean.myDate}"/>

However, it causes trouble when trying to use it with composite components
and gives back the following converter exception and thus can’t update the model…

The (simplified) JSF composite component inputDate.xhtml 

    <head> 
            <title>A date input field</title> 
    </head> 

    <composite:interface> 
            <composite:attribute name="dateValue"/> 
    </composite:interface> 

    <composite:implementation> 
            <h:outputLabel value="MyDateValue" for="input"/> 
            <h:inputText id="input" value="#{cc.attrs.dateValue}"/> 
    </composite:implementation>

Assumption:
It seems the proxy replacement in OpenJPA is handled differently when the value is being accessed from inside a composite. My guess is the EL-resolver handles calls to object values differently when it is passed to composites. Passing it to composites means it is first accessed within the composite, which is too late and the required replacement of the proxy is not accomplished (thus the converter exception)

So I tried to change the Expression Language for MyFaces, but it didn’t work in Websphere, even though I changed the class loading to parent last and provided el-impl and el-api from glassfish in the lib folder and inserted the necessary context-param for MyFaces

How do you guys use JPA-managed dates (or other proxied entities) in composite components???

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If you are using the sun EL implementation you might use the following ELResolver which works around this issue:

    public class BugfixELResolver extends ELResolver {
//...
@Override
public Class<?> getType(ELContext anElContext, Object aBase, Object aProperty) {
    if (aBase.getClass().getCanonicalName().equals("com.sun.faces.el.CompositeComponentAttributesELResolver.ExpressionEvalMap")){
        Object tempProperty=((Map)aBase).get(aProperty);
        if (tempProperty!=null&&tempProperty.getClass().getCanonicalName().equals("org.apache.openjpa.util.java.util.Date.proxy")) {
            anElContext.setPropertyResolved(true);
            return java.util.Date.class;
        }
    }
    return null;
}


}

    Add it to the faces-config this way:

    <el-resolver>
    xxx.BugfixELResolver
</el-resolver>

    This workaround can also be used in environments where you can not change the EL implementation (like websphere etc.).

    • 0