Hi Mike,
Section #10.1.5.2 contains the following:
/The access attribute defines the access type for the embeddable class.
The access attribute overrides
any access type specified by the persistence-unit-defaults element or
entity-mappings
element for the given embeddable class.
Portable applications must not specify the access attribute if mapping
annotations have been applied
to the fields or properties of the embeddable class or the entity with
which it is associated and the value
differs from the access type defined by means of annotations.
Portable applications must not use more than one access type within an
entity hierarchy./
I have two questions:
1) It requires portable applications not to specify an access-type that
is different from what is defined using annotations. That means, a user
can specify conflicting access-type using XML mapping file for an entity
and embeddable class. Is this intentional?
2) Why does this section talk about entity hierarchy?
Thanks,
Sahoo