[
https://issues.apache.org/jira/browse/JOHNZON-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Romain Manni-Bucau resolved JOHNZON-80.
---------------------------------------
Resolution: Fixed
Assignee: Romain Manni-Bucau
When the map is a SortedMap at deserialization time then the attributeorder is
now respected, a simple Map will still have a "hash" ordering.
> 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
> Assignee: Romain Manni-Bucau
> Fix For: 1.1.4
>
>
> 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.
> edit: After discussion it seems this shouldn't be done automatically with the
> AttributeOrder. Instead it might be considered to have an additional flag
> like {{sortMaps}} on the MapperBuilder to get the desired behavior.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
