logoalt Hacker News

pronyesterday at 5:52 PM2 repliesview on HN

Because JSON types don't cleanly map to Java types. For example, a JSON number could be an int, a long, a double, a BigInteger, or a BigDecimal. Which of them the Java code wants is not something you can deduce (most generally, you could represent all JSON numbers as BigDecimal, but that's not very convnient in Java code, so in most cases you'd want to convert that to a primitive type of your choosing anyway). A JSON array is heterogeneous, while Java code typically want to be homogeneous. Representing a JSON array as a `List<Object>` won't work because the conversion of the element types is ambiguous (e.g. numbers).


Replies

prplyesterday at 6:34 PM

Yeah you could go with just Number though, and then keep almost everything a BigInteger/BigDecimal under the covers (or dynamically choose the correct class)

show 1 reply
Hackbratenyesterday at 6:19 PM

Good point for parsing. However, the example is about serialization. What mapping ambiguity do you see there?

show 1 reply