|
Change By:
|
Gail Badner
(25/Jul/12 1:27 PM)
|
|
Description:
|
Here are the cases listed in JSR 317:
Section
11.1.15 for @EmbeddedId
Section 11.1.19 for @IdClass
Section
2.4.1.3 for derived identities:
Example 1 case a) Parent: Single @Id / Dependent: @IdClass
Example 1 case b) Parent: Single @Id / Dependent: @EmbeddedId
Example 2 case a) Parent: @IdClass / Dependent: @IdClass
Example 2 case b) Parent: @IdClass / Dependent: @EmbeddedId
Example 3 case a) Parent: @EmbeddedId / Dependent: @IdClass
Example 3 case b) Parent: @EmbeddedId / Dependent: @EmbeddedId
Example 4 case a) Parent: @Single Id / Dependent: Single @Id is @OneToOne
Example 4 case b) Parent: @Single Id / Dependent: Single @Id and separate @MapsId on @OneToOne
Example 5 case a) Parent: @IdClass / Dependent: @IdClass @Id is @OneToOne
Example 5 case b) Parent: @IdClass / Dependent: @EmbeddedId and separate @MapsId on @OneToOne
Example 6 case a) Parent: @EmbeddedId / Dependent: @IdClass @Id is @OneToOne
Example 6 case b) Parent: @EmbeddedId / Dependent: @EmbeddedId and separate @MapsId on @OneToOne
|
|
Summary:
|
Create binding and relational state classes
Add support
for
composite
derived
IDs
to new metamodel
|
