question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

unnecessary warning was shown resteasy-reactive

See original GitHub issue

Describe the bug I got the message when resteasy-reactive project.

(build-70) [io.quarkus.resteasy.common.deployment.ResteasyCommonProcessor] null: Quarkus detected the need for Mutiny reactive programming support, however the quarkus-resteasy-mutiny extension was not present. I used quarkus-resteasy-reactive-jackson with below dependency.

<dependency>
  <groupId>io.quarkus</groupId>
  <artifactId>quarkus-resteasy-reactive-jackson</artifactId>
</dependency>

In my understanding if I added resteasy-reactive-jackson, then it includes automatically .

<dependency>
    <groupId>io.smallrye.reactive</groupId>
    <artifactId>mutiny</artifactId>
</dependency>

So, I don’t need add “quarkus-resteasy-mutiny” extension, although I use Uni/Multi.

I think that is happened when I add two dependencies quarkus-keycloak-admin-client and quarkus-smallrye-jwt for other purpose.

Could you please let me know to remove this “WARN”, when I see RestEasyCommonProcessor" code, it is checked RESTEASY_MUTINY for capability, but seems like need to check other way which can be used for smallrye reactive.

I suspect that warning is because “quarkus-keycloak-admin-client” use resteasy class

Expected behavior if there is below dependency for mutiny in quarkus-resteasy-reactive-jackson <dependency> <groupId>io.smallrye.reactive</groupId> <artifactId>mutiny</artifactId> </dependency>

the warning message should not be shown.

(build-70) [io.quarkus.resteasy.common.deployment.ResteasyCommonProcessor] null: Quarkus detected the need for Mutiny reactive programming support, however the quarkus-resteasy-mutiny extension was not present. I used quarkus-resteasy-reactive-jackson with below dependency.

(Describe the expected behavior clearly and concisely.)

(Describe the actual behavior clearly and concisely.)

To Reproduce Add this two dependency, then this warning was shown.

<dependency>
  <groupId>io.quarkus</groupId>
  <artifactId>quarkus-resteasy-reactive-jackson</artifactId>
</dependency>
<dependency>
  <artifactId>quarkus-keycloak-admin-client</artifactId>
  <groupId>io.quarkus</groupId>
</dependency>

Link to a small reproducer (preferably a Maven project if the issue is not Gradle-specific).

Screenshots (If applicable, add screenshots to help explain your problem.)

Environment (please complete the following information):

  • Output of uname -a or ver:
  • Output of java -version:
  • GraalVM version (if different from Java): GraalVM 11
  • Quarkus version or git rev:
  • Build tool (ie. output of mvnw --version or gradlew --version):

Additional context (Add any other context about the problem here.)

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:14 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
FroMagecommented, Apr 28, 2021

I think it could be named “Unexpected transitive import of resteasy when using resteasy-reactive”. Thanks to you for reporting 😃

0reactions
thuringiacommented, Apr 28, 2021

I’ll be happy to, what do we want to call the new issue, so that we can properly separate it from this one? Otherwise I’d call it “resteasy-reactive extension imports non-reactive versions transitively”,

Also, a really big thank you for your quick help. I, and everyone on my team, really appreciates it.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Errors after switching to quarkus-resteasy-reactive
The release notes for 2.8 tell me I should switch to quarkus-resteasy-reactive and it's a 1:1 replacment and no changes are necessary.
Read more >
RESTEasy Reactive - To block or not to block - Quarkus
When we introduced RESTEasy reactive, we decided to use a non-blocking approach by default: if not stated otherwise, it calls the HTTP endpoint ......
Read more >
Quarkus Insights #82: What's new in RESTEasy Reactive
Clement Escoffier @clementplop & Georgios Andrianakis @geoand stop by to discuss the latest changes to RESTEasy Reactive and Quarkus.
Read more >
RESTEasy Reactive Blocking vs Non-Blocking by default
As we start to push users more towards RESTEasy Reactive I think the non-blocking by default behaviour is problematic for new users. For...
Read more >
RESTEasy JAX-RS - JBoss.org
Pluggable reactive types: RxJava 2 in RESTEasy; 40.5. ... This will configure WildFly to use new versions of the modules listed in Section...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found