You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@johnzon.apache.org by "Romain Manni-Bucau (Jira)" <ji...@apache.org> on 2021/06/06 07:12:00 UTC

[jira] [Updated] (JOHNZON-146) Mapper json processing should use the order in the Json, not setters

     [ https://issues.apache.org/jira/browse/JOHNZON-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Romain Manni-Bucau updated JOHNZON-146:
---------------------------------------
    Fix Version/s:     (was: 1.2.13)
                   1.2.14

> Mapper json processing should use the order in the Json, not setters
> --------------------------------------------------------------------
>
>                 Key: JOHNZON-146
>                 URL: https://issues.apache.org/jira/browse/JOHNZON-146
>             Project: Johnzon
>          Issue Type: Bug
>          Components: JSON-B, Mapper
>    Affects Versions: 1.1.5
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>            Priority: Minor
>             Fix For: 1.2.14
>
>
> Currently we do a loop over all the getters and try to find the attribute in the JSON.
> But for deduplicateObjects handling one might end up getting a JsonPointer before the original object got processed. 
> This means that we should do it exactly the other way around: loop over the json attributes and then use the setter accordingly.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)