Introduce HttpJakartaServletRequestTags #3923
Closed
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.
Prior to this commit,
HttpRequestTags
would provide Tags for bothjavax.*
andjakarta.*
variants ofHttpServletRequest
. While theHttpServletRequestTagsProvider
andHttpJakartaServletRequestTagsProvider
are separate interfaces, theyboth use
HttpRequestTags
and import all types exposed on its methods.It is strongly advised not to import both
javax.*
andjakarta.*
variants in a typical application and the current arrangement prevents
this best practice.
This commit deprecates Jakarta methods variants in
HttpRequestTags
andmoves them to
HttpJakartaServletRequestTags
. This allows a cleandependency setup for Jakarta apps and a migration path for all in the
meantime.
Closes gh-3804