[Bug] jackson

[niuhutao]

spring boot 3.3.4
SBA 3.3.6

When there is a custom objectmapper in the application, the SBA serialization error will be reported, if the SBA uses special serialization rules, why not build its own objectmapper inside the SBA. Good components should be compatible and fault-tolerant, but SBA has so far been too difficult to use in complex projects

[niuhutao]

Add a little more
I added a special objectmapper in MappingJackson2HttpMessageConverter

[SteKoe]

Hi @niuhutao,

Spring Boot 3 has implemented an isolated object mapper as the docs say :

Responses from the actuator endpoints shipped with Spring Boot 3 now use an isolated ObjectMapper instance to ensure results are consistent.

As long as you do not change the behavior of the isolated object mapper, we are safe and good to go here.

[erikpetzold]

@niuhutao as @SteKoe wrote, Spring Boot 3 provides a separate ObjectMapper for actuator endpoints. This makes sure that you do not change the actuator output by accident.

I guess you have completely overridden the mechanism in your MappingJackson2HttpMessageConverter. This one extends AbstractJackson2HttpMessageConverter and there is a Map with objectMapperRegistrations, probably you should have placed your own ObjectMapper in this Map instead of overriding everything.