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 2016/05/31 07:23:13 UTC

[jira] [Resolved] (JOHNZON-80) Serialization of Maps should take AttributeOrder into account

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

Romain Manni-Bucau resolved JOHNZON-80.
---------------------------------------
    Resolution: Not A Problem

Hello Robert,

AttributeOrder is for cases where ordering is undefined or static.

Maps have an order if desired and johnzon just respects the order you give it (entrySet()).

The solution is to give to johnzon a SortedMap. Cost of sortering of a map would be really higher than for an object and it is not a blocker so closing as not a problem for now.

> Serialization of Maps should take AttributeOrder into account
> -------------------------------------------------------------
>
>                 Key: JOHNZON-80
>                 URL: https://issues.apache.org/jira/browse/JOHNZON-80
>             Project: Johnzon
>          Issue Type: Improvement
>          Components: Mapper
>    Affects Versions: 0.9.2-incubating
>            Reporter: Robert Panzer
>
> MapperBuilder allows to pass a java.util.Comparator to define the AttributeOrder, e.g. write Object properties in their lexicographic order.
> It seems that this order is ignored when java.util.Maps are serialized.
> It would be nice if the AttributeOrder would be used in this case as well.
> Tested on Johnzon 0.9.2-incubating, but looking at the current master it seems that this behavior is still in place even though the code was a bit refactored.



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