-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
RESTEasy Reactive: UniInvoker signatures are wrong #15852
Milestone
Comments
/cc @geoand, @stuartwdouglas |
Huh, public interface CompletionStageRxInvoker extends RxInvoker<CompletionStage> {
@Override
public CompletionStage<Response> get();
@Override
public <T> CompletionStage<T> get(Class<T> responseType); But interestingly it also overrides |
That does sounds reasonable |
stuartwdouglas
added a commit
to stuartwdouglas/quarkus
that referenced
this issue
Mar 23, 2021
gsmet
pushed a commit
to stuartwdouglas/quarkus
that referenced
this issue
Mar 23, 2021
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Mar 23, 2021
Fixes quarkusio#15852 (cherry picked from commit 76409e1)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Due to how we implement it, all its return types are
Uni<?>
instead of the more usefulUni<R>
for methods like<R> get(Class<R>)
, forcing users to cast the return types to the right type:This is because we implemented it with:
Now, for some reason the JAXRS interface is:
Which is pretty useless. We could mitigate this by making
UniInvoker
generic.Or we could do like for
MultiInvoker
(for some reason this does pass the Java type system):Perhaps we should do both (generify and fix the signature via that weirdly allowed covariant override)?
The text was updated successfully, but these errors were encountered: