I’m having the same exception. Strange is that the IDENTICAL codebase runs without errors under Toplink JPA. I’ve only changed the provider and properties in the persistence.xml and included the OpenJPA jars to the project. (That is what JPA should be able to do, afterall.) -- View this message in context: http://www.nabble.com/Open-JPA-error-Could-not-locate-metadata-for-the-class-using-alias-tf3561516.html#a10095774 Sent from the open-jpa-dev mailing list archive at Nabble.com.
- Open JPA error-Could not locate metadata for the class u... saidulu chitipolu
- Re: Open JPA error-Could not locate metadata for th... Jacek Laskowski
- RE: Open JPA error-Could not locate metadata for th... Pinaki Poddar
- Re: Open JPA error-Could not locate metadata fo... Marina Vatkina
- Re: Open JPA error-Could not locate metadata for th... tbee
- Re: Open JPA error-Could not locate metadata fo... Jacek Laskowski
- Re: Open JPA error-Could not locate metadat... tbee
- Re: Open JPA error-Could not locate met... tbee
- Re: Open JPA error-Could not locat... Jacek Laskowski
- Re: Open JPA error-Could not l... tbee
- Re: Open JPA error-Could n... Jacek Laskowski
- Re: Open JPA error-Could not locat... Marina Vatkina
- Re: Open JPA error-Could not l... tbee
- Re: Open JPA error-Could n... Marina Vatkina
- Re: Open JPA error-Could n... tbee