Another question we have is what exactly was the internal test
regression that caused the rollback?
The company I work for (IBM) does a huge amount of functional server based
testing internally. When changes are made, the OpenJPA unit tests are the
first line of tests and occasionally the UTs
Is it possibly some sort of classloading issue? I know in the past we've
seen the 'The name x is not a recognized entity or identifier. Perhaps
you meant n' in the past, but it seems like most of those were cleaned up.
One shot it the dark would be to try to enable property name=openjpa.
As I eluded to in the JIRA, the root problem is that in the JPA 2.0 spec,
the concept of Cache/CacheStoreMode/CacheRetrieveMode/etc/etc was added
and
this change was not honoring that contract. The crux of the problem is
that
the default value for CacheStoreMode is USE and the spec says[1] that
