'Many To One' attribute type should not be 'Persistence Entity'

Question

I'm trying out IntelliJ IDEA and it's warning me of a Hibernate association that I don't quite understand.

One Side:

@Entity
@Table(name = "MY_REQ_ASSIGNEE")
public class MyRequestAssignee extends BaseUser {
    //...
    @OneToMany(fetch = FetchType.EAGER, cascade = {CascadeType.ALL}, mappedBy = "myRequestAssignee")
    private Collection<MyRequest> myRequests = new ArrayList<>();
    //...
}

Many Side:

@Entity
@Table(name = "MY_REQUEST")
public class MyRequest implements Persistable {

   //...
   @ManyToOne(fetch=FetchType.EAGER)
   @JoinColumn(name="ASSIGNEE_ID")
   private MyRequestAssignee myRequestAssignee;
   //...
}

(Persistable is just an interface that has the id property to make sure Hibernate has access to it.)

I see the MyRequestAssignee type underlined in red and the message reads 'Many To One' attribute type should not be 'Persistence Entity'. Are there something wrong with my relationships?

For a sanity check, I looked at this post and this post too.

I have a similar problem with my `@ManyToMany` relationship. The code works, though — Sergey Zolotarev, Apr 19 '23 at 03:02

score 110 · Accepted Answer · answered Nov 05 '15 at 16:58

110

I found this to be caused by the child entity not being defined in hibernate.cfg.xml. The error message could be improved.

answered Nov 05 '15 at 16:58

Phil Carter

1,265
1
10
9

3

Adding `` to the hibernate.cfg.xml resolved this. – riddle_me_this Nov 05 '15 at 21:43
Awesome. I should have been more explicit about what to add to hibernate.cfg.xml. – Phil Carter Nov 09 '15 at 19:08
3

If you are using JPA, it might be an entry in the persistence.xml that's missing. – TheChrisPratt Jan 15 '16 at 19:00
2

@TheChrisPratt Correct. Or it could be in your `annotatedClasses` property of your `LocalSessionFactoryBean` bean config for Spring. – riddle_me_this Jan 21 '16 at 17:02
Using JPA, it means that the entity MyRequestAssignee has to be added in persistence.xml – Marc Bouvier Jul 06 '16 at 07:51
1

If you are using annotations instead of XML, you need to add a @ManyToOne annotation to your field. See this answer: https://stackoverflow.com/questions/3927091/save-child-objects-automatically-using-jpa-hibernate – Janac Meena Jan 14 '20 at 20:00

score 1 · Answer 2 · answered Feb 01 '22 at 07:40

1

I'm getting this issue in my multi-module Gradle project with Quarkus in IntelliJ, where I have a OneToOne reference from an entity of module A to an entity of module B.

The code works, so I guess it could be a false flag of IntelliJ

answered Feb 01 '22 at 07:40

Marian Klühspies

15,824
16
93
136

1

Did you check if your AuthUser had the @Entity annotation? – V. Dimitrov Dec 11 '22 at 17:36
@V.Dimitrov yes, the issue was explicitly related to the multi-Module structure – Marian Klühspies Dec 21 '22 at 17:28

score 0 · Answer 3 · answered Jan 29 '18 at 14:47

0

This question is a bit old, but I just wanted to add that this can also be caused by a conflicting hibernate .hbm mapping file and JPA annotations. I ran into this error message when converting old mapping files to annotations and forgot to comment out one of the old mapping files.

answered Jan 29 '18 at 14:47

Travieso

427
3
13

14

Another reason for this error can be if you forget to add the `@Entity` attribute to your target class. I ended up here when searching for this (even though that wasn't OP's problem) – MetalMichael Mar 19 '20 at 16:40
@MetalMichael you are a saviour – Makari Kevin Aug 23 '23 at 21:51

'Many To One' attribute type should not be 'Persistence Entity'

3 Answers3