Community
Participate
Working Groups
Since there is new functionality where @Embeddable extends @MappedSuperclass in bug # 283028 we need to see how this affects IdentifiableType (which does not include Embeddables) Specifically that the MappedSuperclass accessors are now stored on the Project by the higher ClassAccessor instead of the EntityAccessor and movement of MS discovery to the EmbeddableAccessor >see the relationship between the types in http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/metamodel_api#Types_Hierarchy >Add metamodel test model coverage for @Embeddable extending @MappedSuperclass >Note that @Id support is not extended to Embeddables so the fact it extends an IdentifiableType may be a non issue - we will know during testing >Verify support for and extend the metamodel test model - EmbeddableTypeImpl changes - (non-Id) Embeddable key type in Maps (MapAttributeImpl constructor) (where a MS is at the root) - verify that we can keep EmbeddableTypes as only Managed and not Identifiable >We need some scenarios like the following with varying @Id positioning that will not flow through to the Embeddable MS <-- MS <-- Emb MS <-- Emb <-- ? MS <-- Emb
>See also Embeddables extending Entities by way of a MappedSuperclass(s) in the middle http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/metamodel_api#Missing_Test_Model_Attributes E <-- MS <-- MS <-- Emb E <-- MS <-- Emb
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
