jackson-modules-java8 VS Gson

Ah I forgot you have to explicitly register the JavaTimeModule, did you do that when creating the object mapper? See https://github.com/FasterXML/jackson-modules-java8

Here's the source code. It uses the ISO-88601 format without timezone modifier, e.g. "2021-10-25T00:23:12" – or in other words the same format as LocalDateTime.toString().

Let's say you have a REST API that returns customers. The service layer would talk to repository layer which would talk to the entity layer to ultimately get the Customer object. It makes the most sense just to return Optional to the controller, and using a certain serialization module, the Optional would automatically get translated to JSON.

Most of the time is spent in JSON parsing, specifically in AccessLogAggregator.parseLineJson. Within parsing, the majority of time is spent in org/json/JSONObject.. Since there are faster JSON libraries available, we'll switch to Gson and repeat the tests. To do this, we'll add the following method to our code:

In this concrete example we'll create 3 products. We can then convert this JSON to the list of products using Gson.

Gson has been in maintenance mode for at least 6 years. It's kind of a shame, because the API and implementation were a lot cleaner than Jackson.

For more information on native-image build arguments, please consult the GraalVM Native Image Options documentation. The next listing contains the contents of reflect.json, which contains a bunch of data classes that we need to serialize and deserialize with Gson, as well as our Lambda handler class which the runtime needs to instantiate based on the qualified class name passed to the Lambda function.

The loadModel() method is special. It needs to dynamically update the model path specified in the JSON-formatted template file according to the extraction path of the Jar package. Gson can be used to load and update the JSON object.

If you check out the Gson user's guide, there's a section titled "JSON Field Naming Support" which explains how to do this. There are also lots of examples if you google "gson rename field".

gson

I am not sure if this is what you are looking for, but allot of projects that I worked on used gson to convert between Java objects and JSON strings (https://github.com/google/gson). Maybe you should check it out.

Since this JSON contains the JSON representation of Java objects that are unknown in PoSh/.NET, all you could do is extract the provided object data (values), but not the objects themselves. In order to extract the "real" objects as they're defined, you'd have to start from the Java side, and use a tool like Gson.