Community
Participate
Working Groups
Build Identifier: 2.1.2.v20101206-r8635 If entities in project use complex primary key containing other entity and use JOINED inheritance insertion of data fails on commit. For inheritance SINGLE TABLE work fine. As can be see in logs problems probably on previous insert without all mandatory fields. Reproducible: Always Steps to Reproduce: 1. Create entity A 2. Create entity Parent with key based on A and int fields 3. Create entity Child with key based on A and int fields and referencing Parent 4. Create entities ChildX and ChildY extends the Child 5. Try to insert data in such structure or 1. Create DB using test.sql from the attached project (tested on PostgreSQL 9.0) 2. Run Test class in attached project
Created attachment 189081 [details] The log file
Created attachment 189082 [details] The zipped eclipse project Script for create database in src/jpa/test.sql
Can be avoid if add the duplicated reference to key entity in derived classes (ChildX and ChildY) in project. Like this: @ManyToOne @JoinColumn(name="a_id") public A getA_() { return getA(); } public void setA_(A a) { setA(a); } but occurs error at read data, see bug 337297
Setting target and priority. See the following page for the meanings of these fields: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines Community: Please vote for this bug if it is important to you. Votes are one of the main criteria we use to determine which bugs to fix next.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
