I think that there were some JIRA issues with aliases in 0.9.6. I thought that most of them had to do with orm.xml processing, but maybe some of them were more low-level than that.
Could you try out the almost-final OpenJPA 0.9.7 bits instead? The candidate (currently being voted on) is at http://people.apache.org/~mikedd/staging-repository/org/apache/openjpa/o penjpa-project/0.9.7-incubating/openjpa-project-0.9.7-incubating-binary. zip If that doesn't work out, could you package up an example for us to try out against the latest code? -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: Tuesday, April 24, 2007 11:04 PM > To: open-jpa-dev@incubator.apache.org > Subject: RE: Open JPA error-Could not locate metadata for the > class using alias > > > > > Patrick Linskey wrote: > > > > What's the OpenJPA version in question? > > > > > openjpa-project-0.9.6-incubating-binary > -- > View this message in context: > http://www.nabble.com/Open-JPA-error-Could-not-locate-metadata > -for-the-class-using-alias-tf3561516.html#a10174891 > 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.
