-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
allow custom jakarta.ws.rs.ext.RuntimeDelegate
via configuration
#44301
Comments
/cc @radcortez (config) |
Thanks for reporting! Mind providing a sample application that shows what you were doing and stopped working? In an case, #44335 should take care of the problem for native |
Allow for using RuntimeDelegate SPI in native mode
Sure I can cobble something together. Are you saying #44335 fixes the problem? I had created a |
If it doesn't work, I certainly want to see what's going 🙂 |
Fixes: quarkusio#44301 (cherry picked from commit 4af3754)
Description
We have a requirement where we need to use our own
jakarta.ws.rs.core.UriBuilder
when using quarkus REST.We originally registered our implementation via the java service loader and this work in dev mode but stoped working in prod mode.
We got around this issue by calling
jakarta.ws.rs.ext.RuntimeDelegate::setInstance
in a startup method. It would be great if there was a configuration that could be set to defind the RuntimeDelgate to use. If this optional field is missing, then the default jboss delegate can be chosen.Implementation ideas
The runtime delegate is defined in the
ResteasyReactiveCommonProvessor
class on line 342 on tag3.16
.It seems like this could be executed conditionally based on a configuration value.
The text was updated successfully, but these errors were encountered: