You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
public class BaseClass
{
@Convert(converter=MyConv1.class)
MyType myField;
}
@Convert(attributeName="myField", converter=MyConv2.class)
public class SubClass
{
...
}
This will mean that when checking if a field has a converter we need to go via the ClassMetaData, which will find out for the member, firstly checking for class-level overrides, then member specifications.
The text was updated successfully, but these errors were encountered:
I believe that the member (field/property) annotation should override the type (class) default specification. So by default, if a member is of a type that is defined as having a converter and has no annotation, the member uses that converter. But a member could still override that default by explicitly naming a different converter via an annotation.
With a JPA @convert we can then do
This will mean that when checking if a field has a converter we need to go via the ClassMetaData, which will find out for the member, firstly checking for class-level overrides, then member specifications.
The text was updated successfully, but these errors were encountered: