Must every Entity Bean be registered in persistence.xml?

Question

I'm using Eclipse Facets for JPA 2.0 and Hibernate 4.2 implementation. I think I recall that in previous project I would not have to register an Entity Bean in the persistence.xml. Am I mistaken?

Annotating a POJO (in this case Pub.java) with @Entity will throw the following error in the Eclipse marker/problem view:

Class "com.jacky.webapp.model.Pub" is managed, but is not listed in the persistence.xml file    Pub.java    /webapp/src/main/java/com/jacky/webapp/model

Any clue? thanks.

Nope, I did not. In general, must every Entity Bean be registered with Java EE 6 and it's corresponding JSR JPA implementation? — feder, Aug 05 '13 at 06:19
Check this answer: http://stackoverflow.com/a/21622259/1875434 — abbas, Feb 07 '14 at 08:04

score 33 · Answer 1 · answered Nov 26 '13 at 08:28

As already written here is the solution:

Check you JPA project properties and be sure to select "Discover annotated classes automatically" in the "Persistent class management" section. Doing this should provide the correct validation for your use case.

score 1 · Answer 2 · edited May 23 '17 at 12:10

1

in jpa you have to compile a file called persistence.xml where you tell Hibernate which classes will be managed by your ORM.
Check this question and its accepted answer

edited May 23 '17 at 12:10

Community

1
1

answered Aug 05 '13 at 06:17

Luca Basso Ricci

17,829
2
47
69

1

Bellabax, I noticed, that you could tag the classes to overcome the object-relational impedance. However, that is declarative, and I'd rather apply the annotation style. I just got confirmed from a co-worker, that my assumption/memory is true. No need to register classes manually in the peristence.xml or orm.xml if you use annotations. Presumably, this error must be an Eclipse (4.3 Kepler) error. – feder Aug 05 '13 at 06:30
But is your code work fine during run? I thought you have problem during execution. Probably you are right and is just an eclipse validator problem – Luca Basso Ricci Aug 05 '13 at 06:53
Yes, works fine when manually deployed (Eclipse refuses to deploy errornous WARs). Yes, looks like a Kepler error. I try with Juno later this day. – feder Aug 05 '13 at 07:45
Lookup [here](https://bugs.eclipse.org/bugs/show_bug.cgi?format=multiple&id=392702): maybe is a voluntary warning message... – Luca Basso Ricci Aug 05 '13 at 07:53
Yes, I previously wrote Karen (Dali developer) about it. – feder Aug 05 '13 at 09:25

score 0 · Answer 3 · answered Jun 30 '17 at 16:28

0

It's possible when you created the project, you picked "JPA project" instead of "java Project". In case you don't see "Java Project", follow the "other" and under the wizard type "java" to see the "Java Project".

answered Jun 30 '17 at 16:28

Arash

1
1

Must every Entity Bean be registered in persistence.xml?

3 Answers3

Linked