openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Prud'hommeaux <>
Subject Re: how to disable toplink?
Date Wed, 22 Nov 2006 07:24:59 GMT

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.persisten 
> 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: 
> toplink--tf2683540.html#a7485258
> Sent from the open-jpa-dev mailing list archive at

View raw message