Hi,
we recently switched to static weaving as OneToOne lazy loading did not work in our application (see: http://www.eclipse.org/forums/index.php?t=msg&th=175837& amp;start=0)
We have set the following properties to our persistence.xml and now Eclipselink does not persist a Map/HashMap correctly:
<property name="eclipselink.target-database" value="PostgreSQL"/>
<property name="eclipselink.target-server" value="SunAS9"/>
<property name="eclipselink.weaving" value="static"/>
<property name="eclipselink.weaving.lazy" value="true"/>
<property name="eclipselink.weaving.fetchgroups" value="true"/>
<property name="eclipselink.weaving.internal" value="true"/>
<property name="eclipselink.weaving.eager" value="true"/>
<property name="eclipselink.weaving.changetracking" value="true"/>
In our application we have three classes: UserAccount, UserRole and DataAccessPrivileges. Each UserAccount can have several UserRoles and for each UserRole a UserAccount can have different DataAccessPriviliges.
Stripped down Version of relevant classes:
@Entity
public class UserAccount implements Serializable {
@Id
private Long id;
@OneToMany(fetch = FetchType.LAZY,
cascade = CascadeType.ALL,
targetEntity = DataAccessPriviliges.class,
orphanRemoval = true)
@JoinColumn(name = "useraccount_id")
@MapKeyJoinColumn(name = "userrole_id")
private Map<UserRole, DataAccessPriviliges> dataAccessPrivileges;
}
@Entity
@Table(name = "c_useraccounts_userroles")
public class DataAccessPriviliges implements Serializable {
@Id
private Long id;
@OneToMany(cascade = CascadeType.ALL, orphanRemoval = true, targetEntity = LooselyReference.class)
@JoinTable(name = "c_useraccounts_userroles_dap",
joinColumns = @JoinColumn(name = "useraccounts_userroles_id"),
inverseJoinColumns = @JoinColumn(name = "looselyreference_id"))
private List<LooselyReference> accessibleObjects;
}
DataAccessPriviliges does not have a back-reference to its corresponding UserRole (the key of the map). Our database table that stores our map entrys looks like this:
CREATE TABLE c_useraccounts_userroles
(
id serial NOT NULL,
useraccount_id integer,
userrole_id integer
)
Now when we create for example a new assignment between an existing UserRole with id 4 to an existing UserAccount with id 286 the following querys will be done by EclipseLink:
eclipselink.weaving.changetracking = false:
select nextval(c_useraccounts_userroles_id_seq)
INSERT IGNORE INTO c_useraccounts_userroles (id, lav) VALUES (?, ?)
bind => [20, 14]
UPDATE c_useraccounts_userroles SET userrole_id = ?, useraccount_id = ? WHERE (id = ?)
bind => [4, 286, 20]
eclipselink.weaving.changetracking = true:
select nextval(c_useraccounts_userroles_id_seq)
INSERT IGNORE INTO c_useraccounts_userroles (id, lav) VALUES (?, ?)
bind => [21, 14]
UPDATE c_useraccounts_userroles SET userrole_id = ?, useraccount_id = ? WHERE (id = ?)
bind => [4, 286, null]
As you can see, when changetracking is turned on, then EclipseLink somehow forgets the id = 21 used by the INSERT when EclipseLink wants to UPDATE the table row with the actual assignment between UserRole and UserAccount. So we now have an empty row in our table. When changetracking is set to false, everything works like expected (although its a bit strange that EclipseLink does an insert followed by an update).
Is there anything wrong in our map definition? I don't think so but perhaps I am missing something. For me it looks like a weaving bug.
] 
Search
Help
Register
Login
Home
