jsonbrobot

* **Issue Imported From:** https://github.com/javaee/jsonb-spec/issues/63 * **Original Issue Raised By:**@m0mus * **Original Issue Assigned To:** @m0mus

* **Issue Imported From:** https://github.com/javaee/jsonb-spec/issues/50 * **Original Issue Raised By:**@cyberphone * **Original Issue Assigned To:** Unassigned

@rmannibucau Commented Default is the lexicographic order. However you can use https://github.com/javaee/jsonb-spec/blob/master/api/src/main/java/javax/json/bind/annotation/JsonbPropertyOrder.java to fit your need.

@cyberphone Commented This issue is actually a bit flawed (dated) because ES6 compatible JSON serialization consists of two entirely different things: - Serialization of JSON primitives (Numbers, Literals, and Strings)...

@rmannibucau Commented Hmm, parsing is not (and must not actually to respect the mapping side of the spec) affected at jsonp or jsonb level since it is a bean matching...

@cyberphone Commented For _enveloped_ clear text signatures based on ES6 rules, parsing and serialization are _closely intertwined_. In retrospect I've noted that this complicates the implementation in many JSON APIs,...

@rmannibucau Commented I strongly think we can't change the defaults since they really match today's way of working. However JSON-P (I don't think JSON-B is affected) can get a flag...

@cyberphone Commented > I strongly think we can't change the defaults since they really match today's way of working For my poor understanding only: Does this mean that the Java...

@rmannibucau Commented No, it works well. It just means that normalizing everything is not good since current representation - which is stable/deterministic - is already in used and what is...

@cyberphone Commented That was what I expected. This also means that if the serialization API (JSON-P?) would be enhanced with ES6 compliant serialization of Strings and Numbers (for **int**s, **float**s...