Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

JPA EclipseLink orm.xml and persistence.xml

 
Ranch Hand
Posts: 66
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
All,

I am new to JPA and using Toplink (Oracle's distribution of the open-source EclipseLink) with JPA annotations . I am a bit confused with the purpose of the orm.xml and persistence.xml.

All the JPA based java classes (representative of each underlying database table) should be cataloged in the orm.xml file or persistence.xml file.

I have seen examples on the internet which have entries sometimes in the orm file and sometimes in the persistence file.

Let me know.

Thanks..
 
Ranch Hand
Posts: 553
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The orm.xml file is an option to use to map your entities instead of using annotations, if you are using annotations then you do not need it.

The persistence.xml should technically list all of the persistent classes using the <class> tag, but if all of your classes are in the same jar file as your persistence.xml, then these will be discovered by default in JEE,
and in JSE if you set <exclude-unlisted-classes>false</exclude-unlisted-classes>.
    Bookmark Topic Watch Topic
  • New Topic