私はこれらのテーブルを持っています:
私の意図は次のとおりです。ユーザーはcompany
またはperson
にできますが、それぞれに共通の何かがあります。ユーザー名はemail
とpassword
ので、JPAツールを使用して、この結果のテーブルからエンティティを生成しました。
public class User implements Serializable {
private static final long serialVersionUID = 1L;
@Id
@GeneratedValue(strategy=GenerationType.AUTO)
private int id;
private String email;
private String password;
private int reputation;
//bi-directional one-to-one association to Company
@OneToOne(mappedBy="user", cascade={CascadeType.ALL})
private Company company;
//bi-directional many-to-one association to Location
@OneToMany(mappedBy="user")
private List<Location> locations;
//bi-directional one-to-one association to Person
@OneToOne(mappedBy="user")
private Person person;
//bi-directional many-to-one association to Product
@OneToMany(mappedBy="user")
private List<Product> products;
//bi-directional many-to-one association to UserType
@ManyToOne
@JoinColumn(name="type")
private UserType userType;
//bi-directional many-to-one association to UserPhone
@OneToMany(mappedBy="user")
private List<UserPhone> userPhones;
//bi-directional many-to-one association to UserPicture
@OneToMany(mappedBy="user")
private List<UserPicture> userPictures;
//bi-directional many-to-one association to UserSocialNetwork
@OneToMany(mappedBy="user")
private List<UserSocialNetwork> userSocialNetworks;
// getter and setters
}
ユーザーオブジェクトを永続化しようとすると、EclipseLinkでフォロー例外が起動します。
Exception [EclipseLink-48] (Eclipse Persistence Services - 2.3.0.v20110604-r9504): org.Eclipse.persistence.exceptions.DescriptorException
Exception Description: Multiple writable mappings exist for the field [COMPANY.id_user]. Only one may be defined as writable, all others must be specified read-only.
Mapping: org.Eclipse.persistence.mappings.OneToOneMapping[user]
Descriptor: RelationalDescriptor(entity.Company --> [DatabaseTable(COMPANY)])
Exception [EclipseLink-48] (Eclipse Persistence Services - 2.3.0.v20110604-r9504): org.Eclipse.persistence.exceptions.DescriptorException
Exception Description: Multiple writable mappings exist for the field [PERSON.id_user]. Only one may be defined as writable, all others must be specified read-only.
Mapping: org.Eclipse.persistence.mappings.OneToOneMapping[user]
Descriptor: RelationalDescriptor(entity.Person --> [DatabaseTable(PERSON)])
Runtime Exceptions:
生成されたマッピングは間違っていますか?この例外を解決するにはどうすればよいですか?
更新
public class Company implements Serializable {
private static final long serialVersionUID = 1L;
@Id
@GeneratedValue(strategy=GenerationType.AUTO)
@Column(name="id_user")
private int idUser;
private String email;
private String name;
//bi-directional many-to-one association to Area
@ManyToOne
@JoinColumn(name="area")
private Area areaBean;
//bi-directional one-to-one association to User
@OneToOne(cascade={CascadeType.ALL})
@JoinColumn(name="id_user", insertable=false, updatable=false)
private User user;
// getter and setters
}
@Entity
public class Person implements Serializable {
private static final long serialVersionUID = 1L;
@Id
@GeneratedValue(strategy=GenerationType.AUTO)
@Column(name="id_user")
private int idUser;
@Temporal( TemporalType.DATE)
private Date birthdate;
private String gender;
private String name;
private String surname;
//bi-directional one-to-one association to User
@OneToOne
@JoinColumn(name="id_user", insertable=false, updatable=false)
private User user;
// getters and setters
}
これを行う適切な方法は、@PrimaryKeyJoinColumn
昔ながらの@JoinColumn
。
PersonとCompanyの両方のクラスのinsertable=false, updatable=false
アノテーションに@JoinColumn
を配置する問題を解決しました。
私の推測では、id_userは2回マップされ、1回はBasic @Idマッピングを使用し、もう1回は@ManyToOneを使用します。それらのいずれかを読み取り専用にする必要があります。つまり、insertable/updatable = falseです。または、基本的なIDを削除して、@ Idを@ManyToOneに配置するだけです。