johnzon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Romain Manni-Bucau (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JOHNZON-48) Complex types in collection with converter
Date Sat, 04 Jul 2015 17:02:04 GMT

    [ https://issues.apache.org/jira/browse/JOHNZON-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613964#comment-14613964
] 

Romain Manni-Bucau commented on JOHNZON-48:
-------------------------------------------

Right, sorry was super blury when I reread it.

My point was: we can keep the converter in our mapping model and avoid a lookup for each call,
also the very implicit meaning was when building the model itself we should check for @JohnzonConverter.
Ifit exists and type of the converter is the type of the argument of the parameterized type
then we use it for items.

> Complex types in collection with converter
> ------------------------------------------
>
>                 Key: JOHNZON-48
>                 URL: https://issues.apache.org/jira/browse/JOHNZON-48
>             Project: Johnzon
>          Issue Type: Bug
>          Components: Mapper
>    Affects Versions: 0.9-incubating
>            Reporter: Karl Grosse
>            Priority: Critical
>             Fix For: 0.9-incubating
>
>         Attachments: JOHNZON-48.patch
>
>
> Complex objects in a list get serialized as json object without using registered converters.
This leads to malformed json strings which can't be deserialized if there is no default constructor
available (as is the case with enums). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message