Problem with standalone JPA

Question

I have a stand-alone, non-WLS, utility Spring-JPA jar (jar contains its own META-INF/persistence.xml) that I use across several non-WLS applications. It's using the Toplink provider and works fine. When I attempt to use this jar within a Weblogic 10 war/ear environment, I see random behaviours. Specifically, upon start up of the server environment sometimes the Spring context appears to load all the Toplink entityManager/provider components, and sometimes it does not - in those cases, it appears that an OpenJPA entityManager gets loaded first and nothing works (many errors related to missing openjpa properties). When the Toplink pieces successfully load, all works as expected. It's almost as if the application is experiencing some race condition on what entityManager/provider is being loaded upon startup/deployment of the application.
Please help - I'm at a loss as to how to resolve this issue.
Thanks,
[email protected]

Answer 1

Hello,
Does this work if you set the <exclude-unlisted-classes> tag to true and list your classes in the persistence.xml as described in:
http://www.oracle.com/technology/products/ias/toplink/jpa/howto/java-se-usage.html
If it works, the problem might be with searching the persistence context for entities using a non-url classloader.
Best Regards,
Chris