You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@johnzon.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2017/08/28 06:46:00 UTC
[jira] [Resolved] (JOHNZON-72) Improving Converters
[ https://issues.apache.org/jira/browse/JOHNZON-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Struberg resolved JOHNZON-72.
----------------------------------
Resolution: Fixed
Assignee: Mark Struberg
Fix Version/s: 1.0.0
We submitted a spec change and fixed it in Johnzon-1.0.0 already
> Improving Converters
> --------------------
>
> Key: JOHNZON-72
> URL: https://issues.apache.org/jira/browse/JOHNZON-72
> Project: Johnzon
> Issue Type: New Feature
> Affects Versions: 0.9.3-incubating
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.0.0
>
>
> Converter, Adapter and ObjectConverter are kind of fitting into the same ballpark.
> * Converter: convert from/to a single JSON attribute String
> * Adapter: converts from/to different classes during object de/serialisation
> * ObjectConverter: similar to Adapter, but allows for having much more control over the conversion.
> 1.) I'd like to introduce a common marker interface for them.
> * That could be used for registering a @JohnzonConverter which could be any of the 3
> * That could be used for MapperBuilder#addAdapter() methods
> 2.) ObjectConverter is not a good enough name imo. If you have a better idea, then please shout out ;)
> 3.) We might think about using @Priority on Adapters to allow a fallback chain handling?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)