Honestly, I haven't had time to try to run with your customer handlers... I have been looking ProxyManager code and trying to recreate the initial stack you posted. Here is a small test you can run to see where it is blowing up:
XMLGregorianCalendar cc = null; // instantiate me! OpenJPAEntityManagerFactorySPI emf = (OpenJPAEntityManagerFactorySPI) getEmf(); emf.getConfiguration().getProxyManagerInstance().newCustomProxy(cc, false); // this line should fail for you I haven't been able to recreate the failure on my machine because org.apache.xerces.jaxp.datatype.XMLGregorianCalendarImpl is a final class and org.apache.openjpa.util.ProxyManagerImpl<eclipse-javadoc:%E2%98%82=openjpa-kernel/src%5C/main%5C/java%3Corg.apache.openjpa.util%7BProxyManagerImpl.java%E2%98%83ProxyManagerImpl>.generateProxyBeanBytecode(...) skips trying to create a custom proxy for final types. Thanks, Rick On Fri, Jul 20, 2012 at 1:33 PM, garpinc <garp...@yahoo.com> wrote: > It could be that I didn't implement the AbstractValueHandler correctly. The > api changed from 2.1.2 to 2.2.. now when I restest on 2.1.2 it doesn't work > where it did before.. Please see if you think they are correct.. In the > meantime i'll revert to 2.1.2 and put AbstractValueHandler back to how they > were to see if it then magically works again > > > > -- > Sent from the OpenJPA Users mailing list archive at Nabble.com. > -- *Rick Curtis*
