I have a standalone Spring-JPA utility jar that uses the Toplink provider and works fine standalone and within Tomcat. When I attempt to use this jar within a Weblogic 10 war (within an ear), I see random behaviour. Specifically, on load of the application, sometimes I see the Toplink detailed logging messages indicating the loading of it from within Spring - in that case, all works as expected. Sometimes however, I don't see these messages. In those cases, I get errors attempting to use the classes - specific to OpenJPA and missing properties (as if weblogic has somehow beaten Spring to the punch in creating the entityManger/provider??).

It seems like it might be some type of race condition, as this load behaviour is random (loads/works 2 times, doesn't 3 times, does again once, etc.).

Please help. I think I'm just not understanding the interaction of the container (which I don't even want, just happen to be stuck deploying here) and my independent JPA code.

Thx,
Rick