Community
Participate
Working Groups
Build Identifier: An entity with uni-directional OneToMany property and @MapKeyColumn annotation has the correct database tables created, with the mapping table containing a "key column, but persisting an entity only populates the id columns and not the key column. The persist operation does not throw an error, but subsequent queries soon fail with the following error: Exception Description: The field [ORGANIZATION.MAILINGADDRESSES_KEY] in this expression has an invalid table in this context. This problem occurs when using glassfish-v3.1.1/eclipselink-2.3.0/postgresql/jta as well as a standalone eclipselink-2.3.0 or 2.3.1 using derby and local transactions. A test case will be attached illustrating successful entity persistence, followed by querying the tables showing the nulled key column, and then jpa queries failing. Reproducible: Always Steps to Reproduce: 1. Uncompress attached testcase zip file. 2. Download derby, persistence, and eclipselink jars and put them in src/libs directory. 3. Run ant script in the base directory with the targets "ant clean test" (without the quotes)
Created attachment 207586 [details] testcase zip file
Created attachment 207587 [details] test output
This is possibly the same or similar to bug 344893
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.
This is still present in 2.5.0 using glassfish 4, JavaSE and Derby DB.
Please fix. This is impacting OneToMany Map<String,Object> relationships
Still there in 4.1 Build 13 with EclipseLink 2.5.2, PostgreSQL. Standalone EclipseLink works properly.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
