PathProvider supports Path entities, in preparation for future default support in JAX-RS 4.1 / Jersey 4.1 #5674
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.
Aim
This PR adds support for
Path
entity types in analogy to the existing support forFile
entity types.Justification
In an attempt to modernize JAX-RS and better align it with modern Java, I soon will file a PR for Jakarta REST 4.1 to natively support
Path
entity types by all compliant implementations. As an existing implementation is needed before making an API change part of the specification and TCK, I kindly ask to adopt this new feature to Jersey 3.1 already (as it is optional and non-breaking).Description
This PR only adds optional support for
Path
, not making it part ofMessagingBinders
as it is not yet a mandatory element of the JAX-RS specification, neither in 3.x nor 4.0. In a subsequent PR on the4.x
branch I will later addPathProvider
toMessagingBinders
when agreed to make it part of JAX-RS 4.1.