Odd response to the removal of the toplink jar. The same code with only this change no longer runs the tests. Complains about can't find entity manager. I am starting my investigations but thought I would throw this in the loop to see if someone has seen this before
Phill -----Original Message----- From: Phill Moran [mailto:[EMAIL PROTECTED] Sent: March 25, 2007 10:24 PM To: 'open-jpa-dev@incubator.apache.org' Subject: RE: OPEN-JPA and Toplink 2.0.XX This is exactly what happened and I added my own implementation when I tried to test and got nothing. Well bye bye toplink -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: March 25, 2007 10:04 PM To: open-jpa-dev@incubator.apache.org Subject: Re: OPEN-JPA and Toplink 2.0.XX > On Mar 25, 2007, at 3:24 PM, Phill Moran wrote: > >> This is interesting thanks for the information. Firstly I thought >> that one needed both toplink and JPA to make use of JPA in an >> application. I think I found this on the Glassfish site, can't >> remember now. This is why I posted this here. >> Glassfish distributes TopLink Essentials bundled with the JPA spec jar, so you might have unwittingly acquired TopLink Essentials along with the spec jar and not unsurprisingly, figured that they were the same. Since that experiment at the beginning of the official RI distribution of Java EE 5, the JPA spec jar has been unbundled and is available separately from TopLink Essentials. You are free to use any implementation of the spec that you choose. Craig Craig Russell DB PMC, OpenJPA PPMC [EMAIL PROTECTED] http://db.apache.org/jdo
