Closed liefke closed 6 years ago
As Fastnate does not scan the whole classpath, it can't find every AnyMetaDef
annotation. But it tries to find the named AnyMetaDef
somewhere in the hierarchy of the current class or the hierarchy of the target type of the current attribute, which seems to cover most of the use cases of named AnyMetaDef
annotations.
In addition this issue will fix the support for ManyToAny
, which wasn't working before (never noted due to missing test cases).
When using Hibernates
@Any
annotation on a JPA property, Fastnate supports only@AnyMetaDef
definitions attached to the field itself:But Hibernate supports named
@AnyMetaDef
s at arbitrary positions for example:Fastnate should support these globally defined
@AnyMetaDef
s as well.