Migrating from resteasy to resteasy reacitve APIs give me a 404 #37949
Replies: 4 comments 4 replies
-
Beta Was this translation helpful? Give feedback.
-
Cc @MikeEdgar |
Beta Was this translation helpful? Give feedback.
-
@ramakaruturi , just to clarify - is it that the API does not function at all after the upgrade or just that the OpenAPI documentation is not available? |
Beta Was this translation helpful? Give feedback.
-
Do you index the jar generated here with Jandex: https://github.com/ramakaruturi/openapi-generated ? RESTEasy Reactive is heavily relying on Jandex to set up the endpoints so if your classes are not indexed, they won't be found by RESTEasy Reactive. See https://stackoverflow.com/questions/55513502/how-to-create-a-jandex-index-in-quarkus-for-classes-in-a-external-module for more information about that. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi There,
I have recently tried migrating a project of mine from Quarkus 2.x to 3.x and also switiching from resteasy to resteasy reactive.
While doing that i have observed that my APIs are no longer discoverable i.e. giving 404 after a successful build and deploy.
Upon some digging and trail and error i have narrowed it down and found out its the interfaces that were generated by OpenAPI generator in another jar that i was referring to implement in my project. I have also got a small reproducer here
Project #1
https://github.com/ramakaruturi/openapi-generated
This project uses OpenAPI generator to generate interfaces using JAX-RS and Jakarta EE as a jar file
Project #2
https://github.com/ramakaruturi/petstore-apis
This project consumes the jar file from #1 to implement the interfaces.
If you could please let me know what i could be possibly missing here that the APIs wouldnt be discovered ?
The same setup used to work fine with Quarkus 2.7 and Resteasy.
TIA !!!!
Beta Was this translation helpful? Give feedback.
All reactions