a non-entity [class com.Domain.Groups]and the persistence.xml declaration:
you can clearly see the packages don't match up. Probably removing the <class> elements from the persistence.xml will already fix your problems.
914669 wrote:Not accurate. You may not need it, but when the column name in the database is different from the property name in the entity (for example because the database uses a ridiculous naming scheme), you do need JoinColumn to specify the proper column name. In any other case, Having a JoinColumn annotation does not hurt so I don't see why you offer it as advice.
take this line out:
you don't need both @ManyToOne mapping and the @JoinColumn
914540 wrote:Well I don't use EclipseLink, I use Hibernate. But I believe EclipseLink is bundled with Glassfish and Sun/Oracle isn't going to do that if it breaks on such a trivial thing as this. It must be something really stupid and small, but I'm not seeing it :( Perhaps you should look for a Glassfish forum where you are more likely to find people that use Eclipselink.
I don't understand nobody got this kind of error .
914540 wrote:What error are you getting exactly? The same one you started the thread with?
however even after amending maven dependency & persistence.xml (+ update glassfish server)
I got a hibernate error I fixed and now I got back the same error but I don't understand how it's possible to get an EcliseLink error after modifying the persistance.xml