[
https://issues.apache.org/jira/browse/JOHNZON-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253372#comment-16253372
]
Mark Struberg commented on JOHNZON-146:
---------------------------------------
I got more info where the actual issue is.
Colleagues used the Mapper to serialise the JSON but JAX-RS (and thus JSON-B)
to read the JSON.
And the class to read did have a @JsonbPropertyOder which was different from
the default one (lexical).
Since the Mapper doesn't know about @JsonbPropertyOrder it did write in a
lexical order, but JAX-RS did read the values in the annotated order. -> boom.
> 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
> Fix For: 1.1.6
>
>
> 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
(v6.4.14#64029)
