-
Notifications
You must be signed in to change notification settings - Fork 81
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
Question: Ambiguous Resource Methods in TCK, airlines UserResource #557
Labels
Milestone
Comments
Huh, I hadn't noticed this and I'm not sure if it's valid - would need to check the Jakarta RESTful WS spec for that - but it at least seems unnecessary to test something so confusing here. Before changing it or removing one of the methods, we'd have to go through and check if any tests are expecting these entries to be present and update or remove those tests. |
This was referenced Apr 12, 2023
Closed
This was referenced Apr 20, 2023
Closed
This was referenced May 25, 2023
This was referenced Jun 15, 2023
This was referenced Jul 13, 2023
9 tasks
This was referenced Aug 17, 2023
This was referenced Sep 15, 2023
This was referenced Oct 8, 2023
This was referenced Oct 19, 2023
This was referenced Nov 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In UserResource, two methods have the same path (e.g. refusing to deploy):
and
The only difference is, that
getUserById
defines the parameter asint
, while the first asString
.Is the path parameter type enough to distinguish the methods? So if the parameter is convertible to int, use
getUserById
; usegetUserByName
otherwise? To me it seems wrong, becausegetUserByName
will never work for username made from digits.The text was updated successfully, but these errors were encountered: