json-lib pit

  The entry of a new company, the new company within the network isolation, the external network, not only into. Use of technology architecture, although that has been used SpringBoot, but, all the details are not standardized ah, remember the first day of the downloaded program, are not up and running, looking for a long reason, the original project is not a standard Maven project, should a resources directory, it is a resource, one less s, causes the compiler can not find the resource directory; code is basically no comments to understand thanks to guess, this is for newcomers who are not familiar with the business, really good pain. Thanks to a good salary, I put up with.

  Okay, back to today's topic, json-lib pit. It consists of two pits, one is when deserialized, if the decimal precision is very long, the loss of decimal precision, decimal 8 bits, will now

  Is compatible with a non-standard format string json, json standard format is { "key001": {}} This, however, { "key001" = {}} which it can actually resolved. This was speechless. Because I was doing json-lib replaced when the fastJson, fastJson only supports standard json format, leading to resolution failure

Published 158 original articles · won praise 193 · Views 1.48 million +

Guess you like

Origin blog.csdn.net/zy_281870667/article/details/104714815