Could you post the full stack trace, and maybe some code showing how you're invoking the JPA APIs?
-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: Hans J. Prueller [mailto:[EMAIL PROTECTED] > Sent: Friday, March 23, 2007 5:19 AM > To: open-jpa-dev@incubator.apache.org > Subject: Forgot subject: Strange Could not locate metadata > for the classError? > > -------- Weitergeleitete Nachricht -------- > > > Von: Hans J. Prueller <[EMAIL PROTECTED]> > > Antwort an: open-jpa-dev@incubator.apache.org > > An: open-jpa-dev@incubator.apache.org > > Betreff: No Subject > > Datum: Fri, 23 Mar 2007 13:12:26 +0100 > > > > > > I received a very strange error message from OpenJPA on a > method that is > > being called very often subsequently. The > > most time it works, suddenly it failed with: > > > > Could not locate metadata for the class using alias "PositionLog". > > Registered alias mappings: "{PositionLog=[class > > com.lbslogics.ims.model.PositionLog]}" > > > > It is clearly visible that the used alias is the only one > that is also > > registered. So why does the error happen? > > > > I'm using a nightly-snapshot of last week. > > > > Hans > 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.
