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.
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
Jetty 12 - Simplification of aliases in
PathResource
#8631Jetty 12 - Simplification of aliases in
PathResource
#8631Changes from all commits
97739f9
9e29c95
fcd6e56
a32aa83
db4a44c
882cdd9
a3d9efb
4d39c8a
4411d10
48eaf49
98f25cb
5fb4e65
bbc261c
79cd37d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rename to
resolveAlias()
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with @sbordet, this is a
resolveAlias()
orresolveTarget()
name.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need equals/hashCode at all?
The comparison on
uri
is odd, that's a user-space provided field.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure why we need to compare
PathResource
, I know there are tests for theequals()
but not sure if we actually use it anywhere. But to compare these correctly you need to take theuri
into account.You can come up with examples where two different
PathResource
s have the samepath
field but one is classified as an alias and the other is not. So comparing only onpath
isn't quite correct.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will impact the ResourceService cache though.
The same Resource will exist on multiple locations once this new equals/hashcode exists.
Is that an acceptable behavior?