Tobias - > INFO 07:11:27 - Creating subclass for "[class com.provinzial.framework.util.db.jpa.fetch.B, class com.provinzial.framework.util.db.jpa.fetch.A]". This means that your application will be less efficient ....
It looks like you configured openjpa.RuntimeUnenhancedClasses=true and I'm certain is your problem. Please configure another method of enhancement[1]... Let me know if you have any issues getting your classes enhanced. Thanks, Rick [1] http://openjpa.apache.org/entity-enhancement.html On Thu, Mar 31, 2011 at 12:18 AM, Tobias Trelle < [email protected]> wrote: > Hi Michael, > > > Michael Dick wrote: > > > > Which version of OpenJPA are you using? > > > > I'm using OpenJPA 2.0.1. The database ist DB2 V9. JPA startup log looks > like: > > > INFO 07:11:27 - Using dictionary class > "org.apache.openjpa.jdbc.sql.DB2Dictionary". > INFO 07:11:27 - Creating subclass for "[class > com.provinzial.framework.util.db.jpa.fetch.B, class > com.provinzial.framework.util.db.jpa.fetch.A]". > This means that your application will be less efficient and will consume > more memory than it would if > you ran the OpenJPA enhancer. Additionally, lazy loading will not be > available for one-to-one and > many-to-one persistent attributes in types using field access; they will be > loaded eagerly instead. > INFO 07:11:27 - Starting OpenJPA 2.0.1 > ... > > > > Michael Dick wrote: > > > > It looks like we don't have a cached version of the metadata for type B, > > enabling > > preloading< > http://openjpa.apache.org/builds/latest/docs/manual/manual.html#ref_guide_meta_repository> > ; > > of > > the meta data might at least work around the problem. > > > > Thanks for that hint, but it does not solve the problem. > > Even when I change the fetch type of the b association the eager and load > the A entity by primary key, the error remains the same. > > My persistence.xml looks like this: > > > > com.provinzial.framework.util.db.jpa.fetch.A > com.provinzial.framework.util.db.jpa.fetch.B > true >
