jackson-js | JavaScript object serialization and deserialization library | Serialization library

• Firstly, the json shared in the question is not a valid json. Remove , after "endDatetime": null
• Add @NoArgsConstructor annotation to your DataDto class.
• Register ObjectMapper to disable serialization/deserialization of Instant as timestamp, which it does by default.

Sample code which works for me. I know you are doing via the client but I think this should help you. Either pass a custom object mapper to the client when creating or get the JSON as a string and convert manually.

Do not try to serialize class FlatLightLaf (or any other LookAndFeel class). It is not designed to be serializable and it makes no sense to do so. I'm the author of FlatLaf.

Instead use the class name (as String) of the look and feel.

For searialization use:

Found a simpler solution using marshmallow-union, which is also the recommended way by marshmallow-dataclass: https://github.com/lovasoa/marshmallow_dataclass/issues/62

While you can't use jsonp-filter, you can define a simple filter based on it. For example:

You are breaking the json serialization cycle on the wrong class.

You are sending a list of PostDTO, but applied JsonBackReference to Comments and JsonManagedReference to Posts

Update

Note that ObjectMapper class, JsonManagedReference and JsonBackReference may from 2 packages

• com.fasterxml.jackson.databind.ObjectMapper
• com.fasterxml.jackson.annotation.JsonManagedReference
• com.fasterxml.jackson.annotation.JsonBackReference

or:

• org.codehaus.jackson.map.ObjectMapper
• org.codehaus.jackson.annotate.JsonManagedReference
• org.codehaus.jackson.annotate.JsonBackReference

If you are not consistent between all of them, the mis-matched annotation will be ignored and you will still experience infinite loop during serialization.

There is no obvious issue with your expression. I would debug further to see if response indeed contanis the Json string you posted. The error shows that response exists, but the content differs.

This working example I just created may help you: https://github.com/rob2universe/camunda-http-connector-example

If this does not help, you could share more info, e.g. the process model, server log, service you are calling...

Here is one possible workaround that works only for macOS Swift scripts. It is not for iOS.

We workaround Swift Foundation limitations with a different programming language (Python 2.7 for example).

I'm using Jetty 9.22, I have tried to run the project on different machines with the same Jetty version, the described behaviour is just discovered in some of them.

That's a tell tale sign of multiple copies of the same class in multiple locations.

Since you are using maven, consider running one of the duplicate class detection plugins to find out what you have going on.

• https://github.com/ning/maven-duplicate-finder-plugin
• https://github.com/basepom/duplicate-finder-maven-plugin

You're sending an array of strings for your questionChoices in the JSON body. Your JSON mapper needs to populate a List from this array of strings. So it needs to transform each String into a QuestionChoice object. Presumably, it does that by calling the QuestionChoice constructor that takes a String as argument.

So you're saving a Question which has QuestionChoices which all have a null question property. So you're telling JPA that all QuestionChoices don't have any question (since it's null). So JPA saves what you tell it to save: QuestionChoices without any parent question.

You need to properly initialize the question property of the QuestionChoice.