Skip to content

Jersey-based actuator endpoints not available without ResourceConfig bean #15877

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.

Sign up for GitHub

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

Jump to bottom
Closed
mbhave opened this issue Feb 8, 2019 · 0 comments
Closed

Jersey-based actuator endpoints not available without ResourceConfig bean #15877

mbhave opened this issue Feb 8, 2019 · 0 comments
Labels
type: bug A general bug
Milestone
2.1.3

Comments

@mbhave
Copy link
Contributor

mbhave commented Feb 8, 2019

This issue intended to make jersey-based actuator endpoints available even when the user has not yet configured a ResourceConfig bean. We still need to call the ResourceConfigCustomizer for that to happen.
@mbhave mbhave added the type: bug A general bug label Feb 8, 2019
@mbhave mbhave added this to the 2.1.x milestone Feb 8, 2019
@mbhave mbhave changed the title Jersey-based actuator endpoints not available without a ResourceConfig bean Jersey-based actuator endpoints not available without ResourceConfig bean Feb 8, 2019
@mbhave mbhave closed this as completed in 26da45a Feb 9, 2019
@mbhave mbhave modified the milestones: 2.1.x, 2.1.3 Feb 9, 2019
@dsyer dsyer mentioned this issue Jan 28, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: bug A general bug
Projects
None yet
Milestone
2.1.3
Development

No branches or pull requests
1 participant
@mbhave