> Many thanks Patrick! You're welcome.
FYI, once I commit a fix to OPENJPA-229, you'll be able to use the same class names once again. Sorry about that bug. -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: tbee [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 26, 2007 1:54 AM > To: open-jpa-dev@incubator.apache.org > Subject: RE: Open JPA error-Could not locate metadata for the > class using alias > > > > > Patrick Linskey wrote: > > > > I think that if you do 1, 2, 3, 5, and 6, you should be in > good shape. > > > > This indeed seems to work! > > BTW, Toplink just now also had its lazy loading issue solved: > turns out @MappedSuperclass classes must be listed in the > persistence.xml. The solution actually was unexpected, it > suddenly worked, after you told me to do add them for the > OpenJPA issue. You've solved two issues in one go! :-) > > So now I'm suddenly from no working library to two. Now to > decide which one to use. > > Many thanks Patrick! > -- > View this message in context: > http://www.nabble.com/Open-JPA-error-Could-not-locate-metadata > -for-the-class-using-alias-tf3561516.html#a10196445 > Sent from the open-jpa-dev mailing list archive at Nabble.com. > > 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.
