EclipseLink JPA - location of persistence.xml

java eclipse jpa eclipselink persistence.xml
neid picture neid · Nov 26, 2011 · Viewed 28.8k times · Source

I am using JPA for a java class and having trouble putting the persistence XML file where it should be.

The IDE i am using is Eclipse Helios. Eclipselink jar files are downloaded and added to my JRE System Library and all. I wrote up the persistence.xml with the tag after getting the following error :

Exception in thread "main" javax.persistence.PersistenceException: No Persistence provider for EntityManager named customers

Provider tag:

<provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>

The program still doesn't run so i am wondering where should I place persistence.xml (i.e src/main/resources, or lib/META-INF... etc )

Answer

Ken Chan picture Ken Chan · Nov 26, 2011

persistence.xml should be put inside an directory called META-INF under the root of the classpath .

Right click your project in eclipse ==> Properties ==> Java Build Path . Suppose you configure one of the build paths to be /src/main/resources , then you should put the persistence.xml at /src/main/resources/META-INF/persistence.xml

Related questions

What is a JPA implementation?

I'm getting started with JPA, and I'm confused as to what exactly the JPA implementation(EclipseLink, TopLink, Hibernate, etc.) does. I understand the theoretical role of JPA, but what is the purpose of the various implementations? Are there significant differences …

Read More
javax.persistence.* sources, where?

I might be missing something really obvious here, but I couldn't find the sources for a few classes from the javax.persistence package. I'm using EclipseLink as a JPA provider. When I tried Ctrl+left clicking a method of the …

Read More
Eclipse does not recognize content of persistence.xml

Im getting the following error in eclipse: The persistence.xml file does not have recognized content. My persistence.xml file works great in my application but eclipse keeps giving me this error. I got this after moving the file and …

Read More