ObjectMapper | Simple JSON Object mapping written in Swift | JSON Processing library

Welcome to dependency hell and breaking changes in libraries.

This usually happens, when various lib bring in different version of same lib. In this case it is Jackson. java.lang.NoSuchMethodError: com.fasterxml.jackson.dataformat.xml.XmlMapper.coercionConfigDefaults()Lcom/fasterxml/jackson/databind/cfg/MutableCoercionConfig; means: One lib probably require Jackson version, which has this method, but on class path is version, which does not yet have this funcion or got removed bcs was deprecated or renamed.

In case like this is good to print dependency tree and check version of Jackson required in libs. And if possible use newer versions of requid libs.

Solution: use libs, which use compatible versions of Jackson lib. No other shortcut possible.

You can use retrieve() in combination with onStatus to get access the client response when it is an "error". You can then invoke bodyToMono on it to unmarshall the response to a java object. Depending on the content type of the response body, spring will use the correct decoder. For examaple, if the body is json, it will use an ObjectMapper for unmarshalling.

Register Jackson ParameterNamesModule, which will automatically map JSON attributes to the corresponding constructor attributes and therefore will allow you to use immutable classes.

The problem seems to be caused by how JavaBeans methods get generated when there's a single lowercase character at the beginning of the property name. You might be surprised by the fact that getpId and getcId are indeed correctly named, just as I was.

In short, pId correctly results in the getter getpId rather than the Lombok-generated getPId (the one JavaBeans should have kept, in my opinion).

Now, the interesting part is that Jackson makes cid and pid out of getCId and getPId, respectively, for some reason... while at the same time producing cId and pId for getcId and getpId.

So while getcId and getpId are a quirk of JavaBeans, it seems that Jackson is behaving correctly by default, when the getters are correctly named, i.e., getpId -> "pId" and getcId -> "cId".
Given that Lombok generates getPId and getCId, which lead to the all-lowercase keys in the resulting JSON, deserialization does not work.

If you don't like the getpId/getcId naming, then you may have to write your own getters and force a property name explicitly:

I don't know from where you got only your error message, but it's incomplete. In Terminal.app, if you do $> swift build, you'll get this error:

You have a few options:

• Use Powermock with Mockito to mock the final elements. This will allow you to unit-test all of your code.
• You can use Wiremock or a similar over-the-wire HTTP mocking tool which will allow you to test all of your code in a black-box fashion. All of your code can be tested this way as a black box.
• Refactor you're code and wrap OkHttp classes and methods in your own classes that can be mocked. This still leaves some code untested.

You can use readerForUpdating to create an ObjectReader

Factory method for constructing ObjectReader that will update given Object (usually Bean, but can be a Collection or Map as well, but NOT an array) with JSON data.

and then use the readValue on the ObjectReader:

Method that binds content read from given JSON string, using configuration of this reader. Value return is either newly constructed, or root value that was specified with withValueToUpdate(Object).

in a code similar to this one:

As of 2021 unanswered means it is still not (easy) possible to use an alternative ObjectMapper for the same media/object/response type. I.e.

No, it is not (easy) possible to:

... register Controller specific ObjectMapper in SpringBoot

(..not without "re-implementing" half of spring-web).

But what is (easy) possible:

Is to register custom ObjectMapper per java- and media type (combinations! + wildcards for the media types)! (additionally to the spring-configured "default object mapper")

With:

If dev096.dev.cloud.******.eu is a host used only in production, then your production server needs to know that host; not your local PC, nor Jenkins.

Ideally, you'd run your Jenkins tests using a 'jenkins' Spring profile, and then define the localhost in application-jenkins.properties.