I had trouble with that too, but wasn't able to get to the bottom of it. If you enable debug logging you might be able to spot the root cause.
It's a pain for unit testing, but the best approach might be to just list the classes in persistence.xml with <class> tags. -mike On Tue, Jul 9, 2013 at 4:27 PM, garpinc <garp...@yahoo.com> wrote: > When this executes: > EntityManagerFactory preWrappedEntityManagerFactory = > > Persistence.createEntityManagerFactory(JPAHelperFactory.getInstance().getPersistenceID(), > jpaConf); > > > I get: > 359 jpastor INFO [main] openjpa.Enhance - You have enabled runtime > enhancement, but have not specified the set of persistent classes. OpenJPA > must look for metadata for every loaded class, which might increase class > load times significantly. > 1600 jpastor INFO [main] openjpa.Runtime - OpenJPA dynamically loaded > the class enhancer. Any classes that were not enhanced at build time will > be > enhanced when they are loaded by the JVM. > 1600 jpastor WARN [main] openjpa.Runtime - OpenJPA dynamically loaded > the class enhancer. Any classes that were not enhanced at build time will > be > enhanced when they are loaded by the JVM. > > even though jpaConf has following defined: > openjpa.MetaDataFactory=jpa(Types=the classes... > > Am I missing something? > > > > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/JDK-1-7-seems-to-be-causing-an-issue-with-latest-snapshot-tp7581417p7584373.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. >
