On Sep 16, 2010, at 6:14 AM, Andy wrote: > On 16.09.2010 14:20, Jean-Louis MONTEIRO wrote: >> Hi David, >> >> I checked with OpenJPA guys and this feature has been disabled. >> Have a look here https://issues.apache.org/jira/browse/OPENJPA-651 >> https://issues.apache.org/jira/browse/OPENJPA-651 >> >> But, we can get back to the OpenJPA 1.x behavior using the property >> openjpa.RuntimeUnenhancedClasses=supported. >> >> With this property set, it works fine now. >> Regarding the discussion and the JIRA, it may be great to get a better >> solution. >> >> Jean-Louis >> > Just checked that in ;-)
Definitely a step in the right direction. We'll probably want a fix in OpenEJB rather than requiring all apps to compensate for the OpenJPA change. I swizzled our existing PersistenceProviderProperties class to be aware of the openjpa.RuntimeUnenhancedClasses=supported flag and set it if it isn't found. http://svn.apache.org/viewvc?view=revision&revision=997956 With that we should be able to remove the 'openjpa.RuntimeUnenhancedClasses' flags from all our tests/examples and everything should still work. Might be a good idea to do that so we know the auto-setting support works and users are getting the same experience we are. -David
