Replies: 1 comment
-
RESTEasy is only processed for web archives, WAR's. While other deployment types, e.g. EJB JAR's, will get the dependencies added, they won't be processed like a typical Jakarta REST deployment. The specification itself specifically mentions what should happen in a servlet container and a WAR. Your That said as you see the client does work, however you'd need to use the {{jboss-deployment-structure.xml}} to use the client with the specific dependencies you'd like. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When using resteasy client in an EJB container (i.e: jboss EAP 7.3 environment - resteasy version: 3.15.3.Final), some features arent working as expected.
To name a few:
The property resteasy.preferJacksonOverJsonB can only be setted as a system property (or from servlet context param which are unusable outside a war). This isn't ideal in a context where we deploy multiple application so they don't interfere with each other.
I think the documentation is misleading about that and let us think that this property is settable via microprofile-config. I don't know if I did this correctly but after a quick look at the code, this doesnt seem to be considered.
What would be the correct way to go around that ? The only workaround I found is to exclude the json-binding-provider from my
jboss-deployment-structure.xml
.ContextResolver, be it a
ContextResolver<Jsonb>
or aContextResolver<ObjectMapper>
aren't picked up. In a servlet context, thoses@Provider
are picked up by theListenerBootstrap.getParameter(ResteasyContextParameters.RESTEASY_SCANNED_PROVIDERS)
in ConfigurationBootstrap#L132Any idea how to solve these issues ? If I understood correctly, the documentation only tell us how to bootstrap inside a servlet container which is an obvious prerequisite when serving REST request. But I think that calling REST API from an EJB container isn't a weird usecase.
Beta Was this translation helpful? Give feedback.
All reactions