Interesting point. Roger: you might be able to also get around the problem by using resource injection into an EntityManagerFactory field (with the @PersistenceUnit annotation).
-Patrick -- Patrick Linskey BEA Systems, Inc. _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 22, 2006 11:36 AM > To: open-jpa-dev@incubator.apache.org > Subject: Re: how to disable toplink? > > I looked at the code in > javax.persistence.Persistence.createEntityManagerFactory and it > iterates the META-INF/services/ > javax.persistence.spi.PersistenceProvider using the context class > loader. > > So, first assumption: you are using the > Persistence.createEntityManagerFactory method in your servlet init > method to locate the EMF. > > The issue with this is in Persistence. The results of finding the > services the very first time is cached in a static variable. > The only > way I can see to make this work is to use your own version of > Persistence that is also deployed in your WAR file. If you use the > Persistence.class that is shared in the server, you can never > see the > provider in your WAR file. So you would have to use the non- > delegating WAR file loader along with your own copy of the > persistence.jar that contains Persistence.class. > > If you use the server's JNDI lookup, or put the OpenJPA jar > file into > the server's shared library, you should be able to avoid this issue. > > Craig > > On Nov 22, 2006, at 10:58 AM, Patrick Linskey wrote: > > > My read of the spec is that while this deployment isn't explicitly > > called out, it certainly is strongly implied, and at the > very least an > > appserver should provide clear instructions for how to > deploy OpenJPA > > for use in such an environment. > > > > -Patrick > > > > -- > > Patrick Linskey > > BEA Systems, Inc. > > > > > ______________________________________________________________ > ________ > > _ > > Notice: This email message, together with any attachments, may > > contain > > information of BEA Systems, Inc., its subsidiaries and > > affiliated > > entities, that may be confidential, proprietary, copyrighted > > and/or > > legally privileged, and is intended solely for the use of the > > individual > > or entity named in this message. If you are not the intended > > recipient, > > and have received this message in error, please immediately return > > this > > by email and then delete it. > > > >> -----Original Message----- > >> From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On > >> Behalf Of Marc Prud'hommeaux > >> Sent: Tuesday, November 21, 2006 11:25 PM > >> To: open-jpa-dev@incubator.apache.org > >> Subject: Re: how to disable toplink? > >> > >> Roger- > >> > >> What happens if you put the OpenJPA jars and dependencies in the > >> system classpath of the container? Does it work then? > >> > >> If so, then that might be the only solution, currently. IIRC, the > >> spec doesn't say anything about allowing JPA implementations > >> themselves to be bundled into WARs or EARs, so there might > no be any > >> generic way to do so (which isn't to say that it's impossible; it > >> might just require some container-specific glue to make it work). > >> > >> > >> On Nov 21, 2006, at 11:59 PM, roger.keays wrote: > >> > >>> > >>> Is anybody aware of an effective way to ensure that the > openjpa jars > >>> distributed in a WAR are used for the persistence > >> implementation? I > >>> have > >>> tried > >>> > >>> > >>> <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</ > >>> provider> > >>> > >>> in persistence.xml, and > >>> > >>> > >>> > >> javax.persistence.spi.PersistenceProvider=org.apache.openjpa.p > >> ersisten > >>> ce.PersistenceProviderImpl > >>> > >>> in the emf properties map but neither appear to work. This problem > >>> occurs > >>> when deploying to Glassfish, oc4j and (to a lesser extent) Resin > >>> (resin > >>> provides a buggy ejb30.jar). It seems to be a classloading > >> problem, > >>> because > >>> these containers load the Persistence.class from their own lib > >>> instead of > >>> the webapp's. Since that class can't find openjpa, it just falls > >>> back to > >>> toplink. I had expected the webapp's classes to be loaded in > >>> preference to > >>> the containers though. > >>> > >>> Any suggestions? > >>> > >>> Roger > >>> > >>> > >>> -- > >>> View this message in context: > http://www.nabble.com/how-to-disable- > >>> toplink--tf2683540.html#a7485258 > >>> Sent from the open-jpa-dev mailing list archive at Nabble.com. > >>> > >> > >> > > Craig Russell > Architect, Sun Java Enterprise System http://java.sun.com/products/jdo > 408 276-5638 mailto:[EMAIL PROTECTED] > P.S. A good JDO? O, Gasp! > >
smime.p7s
Description: S/MIME cryptographic signature
