-
Notifications
You must be signed in to change notification settings - Fork 40.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support isolated actuator ObjectMapper #20291
Comments
bclozel
added a commit
that referenced
this issue
Feb 21, 2020
bclozel
added
the
status: pending-design-work
Needs design work before any code can be developed
label
Mar 10, 2020
A second attempt is ongoing, see #20290. |
philwebb
changed the title
Add actuator specific ObjectMapper
Support actuator specific ObjectMapper
Nov 9, 2022
philwebb
removed
the
status: pending-design-work
Needs design work before any code can be developed
label
Nov 10, 2022
philwebb
changed the title
Support actuator specific ObjectMapper
Support isolated actuator ObjectMapper
Nov 10, 2022
philwebb
added a commit
that referenced
this issue
Nov 10, 2022
Add `OperationResponseBody` tagging interface that can be used to trigger the use of an isolated ObjectMapper specifically for actuator responses. The isolated mapper is provided by an `EndpointObjectMapper` bean which is auto-configured unless specifically disabled by the user. WebMVC, WebFlux and Jersey integrations have been updated to provide a link between the `OperationResponseBody` type and the endpoint `ObjectMapper`. See gh-20291
philwebb
added a commit
that referenced
this issue
Nov 10, 2022
Update types returned from endpoints to implement the `OperationResponseBody` interface. This ensures that they will be serialized using the isolated actuator `ObjectMapper`. See gh-20291
philwebb
added a commit
that referenced
this issue
Nov 10, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a new attempt at fixing #12951, since the original fix caused regressions (see #20211).
The text was updated successfully, but these errors were encountered: