: Glassfishv3 + OpenJPA-2.0.0: Enhancer not working
Stefan,
Are you using an injected entity manager or entity manager factory:
@PersistenceUnit
private EntityManagerFactory emf;
or going the application managed route:
emf =
Persistence.createEntityManagerFactory
. The commons-* and serp
libraries are added to Glassfish's lib directory along w/ OpenJPA-2.0.0.jar.
Original-Nachricht
Datum: Mon, 19 Jul 2010 16:26:55 -0500
Von: Jeremy Bauer techhu...@gmail.com
An: users@openjpa.apache.org
Betreff: Re: Glassfishv3 + OpenJPA-2.0.0
Hello,
I have a Glassfishv3 running here and *need* to use OpenJPA-2.0.0.
I'm currently having two different setups in our persistence.xml; here's the
working one:
persistence xmlns=http://java.sun.com/xml/ns/persistence;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
Stefan,
It does not look like your persistent classes are being discovered. I think
I have glassfish v3 installed somewhere, so I'll see if I can reproduce the
issue. BTW, there's a developer's edition of WebSphere Application Server
V7[1] and a feature pack for OSGi/JPA 2.0[2] available for
Doubt the Glassfish enhancer would ever work, as it is being provided by
Eclipselink and enhanced entities are provider specific.
If you're building with Maven, then try using the openjpa-maven-plugin
at build time to enhance them -
http://openjpa.apache.org/enhancement-with-maven.html
For
Stefan,
Are you using an injected entity manager or entity manager factory:
@PersistenceUnit
private EntityManagerFactory emf;
or going the application managed route:
emf =
Persistence.createEntityManagerFactory(myApplicationPersistenceUnit);
?
In my simple test, I found that
Stefan,
I took another look at your stack and it looks like you are using an app
managed persistence unit. It may simplify things for you if you can switch
to using injection to get an instance of the emf.
BTW, I have these libs bundled with my app:
commons-collections-3.2.1.jar
