Skip to content
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

Add support for mutiny types in reactive routes #10379

Merged
merged 5 commits into from
Jul 3, 2020

Conversation

cescoffier
Copy link
Member

Add support for Uni, Multi, and SSE to reactive routes.

@@ -496,25 +473,74 @@ void implementInvoke(BeanInfo bean, MethodInfo method, ClassCreator invokerCreat

ResultHandle paramHandle;
MethodDescriptor methodDescriptor;
String returnType = descriptor.getReturnType().name().toString();

// TODO Make Routing Context optional, allow injected Response and Request individually.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 if a method returns something we should make the context param optional...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've created #10397

Copy link
Contributor

@mkouba mkouba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Except for the inconsistency when returning Multi<String> as described here: #10379 (comment). I don't see a good reason for this behavior.

However, if there are any strong arguments feel free to dismiss my review...

@mkouba
Copy link
Contributor

mkouba commented Jul 3, 2020

JDK 14 failure is unrelated. The ConcurrentExecutionTest.testNonconcurrentExecution() is unreliable. I'll need to address it in a separate PR.

@mkouba mkouba merged commit 2f20cf5 into quarkusio:master Jul 3, 2020
@cescoffier cescoffier deleted the features/reactive-routes-mutiny branch July 15, 2020 14:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants