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
Since 2.6 added new concept of referential types; and since referential types are really quite a distinct value type, it makes sense to improve registration of serializers, deserializers, for the same.
But since Serializers and Deserializers are interfaces, it is not easy to add new methods without breaking backwards compatibility. But there are Base classes, which could relatively easily be augmented to have new methods called for instances of ReferenceType. This would also require addition of another "bean" access method.
It is not 100% clear this is the best approach to take; if not, can close the issue. But I want to record this to keep the idea around until it can be evaluated.
The text was updated successfully, but these errors were encountered:
cowtowncoder
changed the title
(2.7) Add new method in Deserializers.Base to support ReferenceType
(2.8) Add new method in Deserializers.Base to support ReferenceTypeFeb 12, 2016
cowtowncoder
changed the title
(2.8) Add new method in Deserializers.Base to support ReferenceType
Add new method in Deserializers.Base to support ReferenceTypeMay 4, 2016
(and ditto for
Serializers.Base
)Since 2.6 added new concept of referential types; and since referential types are really quite a distinct value type, it makes sense to improve registration of serializers, deserializers, for the same.
But since
Serializers
andDeserializers
are interfaces, it is not easy to add new methods without breaking backwards compatibility. But there areBase
classes, which could relatively easily be augmented to have new methods called for instances ofReferenceType
. This would also require addition of another "bean" access method.It is not 100% clear this is the best approach to take; if not, can close the issue. But I want to record this to keep the idea around until it can be evaluated.
The text was updated successfully, but these errors were encountered: