JBEAP-8013: Impossible to use JAX-RS and Spring MVC in the same WEB app #1032
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@gaol , considering the latest discussion on https://issues.jboss.org/browse/JBEAP-8013, I'm closing this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The fix was locally tested and I am sending it if engineering agree to remove the spring servet dispatcher as a possible bootstrap servlet.
It is important to discuss the impacts on Spring MVC + RESTEasy integration if we remove this bootstrap class. However, it is proven in JBEAP-8013 that it is breaking JAX-RS in Spring MVC apps deployed in EAP/Wildfly.