> It's a bit confusing to be but if you are saying that Hibernate ORM looks for Address#getCountry() then that's clearly a bug.
Not sure whether this is "clearly" a bug. The spec says (section 2.3.3)
The access type of an embeddable class is determined by the access type of the entity class, mapped
superclass, or embeddable class in which it is embedded (including as a member of an element collection)
independent of whether the access type of the containing class has been explicitly specified or
defaulted. A different access type for an embeddable class can be specified for that embeddable class
by means of the Access annotation as described above.
So really it depends also on which class uses Address. If the class embedding Address has property access, then the attributes in Address should be access via property access. Obviously this would create other issues. In this case Adress is used from within Person which indeed had field access. So Address attributes needs to be access via field access and Country attributes via property (due to the explicit _@Access annotation).
Implementation wise we need to check the annotation processing code. There might be still some gaps.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
> It's a bit confusing to be but if you are saying that Hibernate ORM looks for Address#getCountry() then that's clearly a bug.
Not sure whether this is "clearly" a bug. The spec says (section 2.3.3)
So really it depends also on which class uses Address. If the class embedding Address has property access, then the attributes in Address should be access via property access. Obviously this would create other issues. In this case Adress is used from within Person which indeed had field access. So Address attributes needs to be access via field access and Country attributes via property (due to the explicit _@Access annotation).
Implementation wise we need to check the annotation processing code. There might be still some gaps.