Michael Hamburger

I have a similar issue. I tried to migrate fom `resteasy` to `resteasy-reactive` and from `rest-client` to `rest-client-reactive`. Every Client has it's own ObjectMapper which is registered via `@RegisterProvider(....class)`. In...

@geoand You can use this https://github.com/hamburml/context-resolver When quarkus-resteasy-jackson and quarkus-rest-client-jackson is used the GreetingRestClientMapper works (getContext is called). When using quarkus-resteasy-reactive-jackson, quarkus-resteasy-reactive and quarkus-rest-client-reactive-jackson instead of the older counterparts getContext...

Thanks for your answers. Looks like we will stop our migration to reactive dependencies till this is configurable. I am not so sure but I think I read somewhere that...

I also must say that without our api gateway which validates the request body against a scheme I probably would have missed that ContextResolver doesn't work. For me it is...

@michalszynkiewicz and @Sgitario Could you please give a statement to this issue? Thanks!

@vasturiano In our usecase we have more than one charts in one html page. A hardcode change would change every chart. We would need to change this only for some...

This is still not merged. Is it safe to use?

I moved to https://github.com/Mottie/tablesorter I can use usNumberFormat setting to switch between point and comma.

@faermanj It works on my side with quarkus 2.11.1.Final. I set `quarkus.class-loading.reloadable-artifacts=software.amazon.awssdk:dynamodb-enhanced`

@faermanj No, it looks like it does not work :( @debora-ito any news on the prio? @Nithanim If you like you could help here https://github.com/quarkiverse/quarkus-amazon-services/pull/255