Skip to content

Auto-configure a ResourceConfig for Jersey endpoints if needed #11948

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

Closed
wants to merge 1 commit into from
Closed

Auto-configure a ResourceConfig for Jersey endpoints if needed #11948

wants to merge 1 commit into from

Conversation

michael-simons
Copy link
Contributor

Closes gh-11939

@flangknecht
Copy link

Why not go a step further and auto-register spring-managed resources (and by that I mean any component annotated with javax.ws.rs.Path) by class?
This would allow us to stop having to manually enumerate JAX-RS resources and further eliminate boiler plate code from Spring-Boot projects using Jersey.

@wilkinsona
Copy link
Member

@flangknecht That's largely unrelated to this pull request. Please open a separate issue and we can consider what you've proposed in due course.

@wilkinsona wilkinsona added this to the 2.1.0.M1 milestone May 11, 2018
@wilkinsona wilkinsona self-assigned this May 11, 2018
@wilkinsona wilkinsona changed the title Conditionally add an empty ResourceConfig bean Auto-configure a ResourceConfig for Jersey endpoints if needed May 11, 2018
wilkinsona added a commit that referenced this pull request May 11, 2018
* gh-11948:
  Polish "Auto-configure a ResourceConfig for Jersey endpoints if needed"
  Auto-configure a ResourceConfig for Jersey endpoints if needed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement A general enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Conditionally auto-configure a ResourceConfig bean for use by the Jersey-based endpoints
5 participants