You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tend to agree since there is a lot of different ways to configure Jackson, and this one is IMO the less relevant. It only allows to configure 2 properties that could be configured thanks to the spring.jackson.* ones or thanks to a Jackson2ObjectMapperBuilder bean.
Last argument in favor of removing it, current property names (jsonPrettyPrint, jsonSortKeys) may be confusing when using Jackson for XML serialisation.
I'm not a fan of the http.mappers.* configuration either. It tries to provide an abstraction that doesn't work as not all mapping technologies are the same. For example, you can't enable pretty printing with Gson after the Gson instance has been created. Also, as you've pointed out the property names assume JSON which may not be the case.
We could change this for RC2 if we think leaving it is going to ultimately cause more pain. I'm not keen for the property to simply disappear, but the deprecated warning seems fair enough.
The text was updated successfully, but these errors were encountered:
From the comments on 1919:
@sdeleuze:
@wilkinsona:
@sdeleuze:
@philwebb:
The text was updated successfully, but these errors were encountered: