What's the OpenJPA version in question?

-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 10:20 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: Open JPA error-Could not locate metadata for the 
> class using alias
> 
> 
> 
> 
> Marina Vatkina wrote:
> > 
> > This is close to impossible as there are probably CTS tests 
> that use 
> > an @Entity that extends another @Entity. Are you using JPA 
> in an EE 5 
> > container?
> > Otherwise
> > you need to list all antities and mapped superclasses in your 
> > persistence.xml.
> > 
> 
> I did'n't say this didn't work under OpenJPA, it doesn't work 
> under Toplink.
> OpenJPA  continues to have the same exceptions as stated in 
> the origin of this thread, so the @MappedSuperclass is not the reason.
> 
> JSE 1.6.0. 
> 
> All classes are listed in the persistance.xml (because it 
> knows the class in question is persisted, but has trouble 
> finding the metadata).
> 
> 
> --
> View this message in context: 
> http://www.nabble.com/Open-JPA-error-Could-not-locate-metadata
> -for-the-class-using-alias-tf3561516.html#a10165609
> 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.

Reply via email to