-
Notifications
You must be signed in to change notification settings - Fork 80
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
Integration with RESTeasy broken with 2.3 #41
Comments
Specific issue should be fixed, but what I really want to do is figure out a way to guard against basic integration issues if possible. |
There are several tools that can help:
|
Thanks. |
Immediate issue resolved. |
Is this in 2.3.2? |
@night199uk Fix should be in 2.3.2; deprecated methods were added back. Can you provide exception for failure? Perhaps there is some other compatibility issue that causes problems. |
17:49:51,096 ERROR [io.undertow.request](default task-1) UT005023: Exception handling request to /x.x.x.x-x-0.0.1-SNAPSHOT/rest/y/y: java.lang.NoSuchMethodError: org.jboss.resteasy.plugins.providers.jackson.ResteasyJackson2Provider._configForWriting(Lcom/fasterxml/jackson/databind/ObjectMapper;[Ljava/lang/annotation/Annotation;)Lcom/fasterxml/jackson/jaxrs/json/JsonEndpointConfig; All Wildfly jackson libs under modules/ were replaced with their respective 2.3.2 variants. I'm now sure how to dump the classloader to check what wildfly is actually using, and annoyingly the jackson versions are not in the stacktrace, but the 2.3.0 libs were removed from the filesystem so I'm basically certain wildfly is using 2.3.2. Eclipse recognizes the method as deprecated from the 2.3.2 source included via maven in my pom.xml so I don't see any issues there. If there is a class loader issue loading the wrong jackson libs, I can't figure it out. |
I uploaded a simple test project to the wildfly issue here: |
Thanks. |
Hmmh. There seems to be some discrepancy between naming here; error message is missing leading underscore? However since Looking at method definitions (2.2 vs 2.3), this might be something else: maybe it's linkage problem. If so, the problem is that while I added back I will go ahead and add an override, just in case. |
Added explicit overrides for sub-classes, hoping this resolves remaining problem. |
Hmmh. I am not 100% sure how to use the referenced test project; it also does not seem use explicit Jackson version override. |
Can you provide me a package of test jars somehow and I can probably test tonight for you? |
What you can do is build jars locally using 'mvn deploy', and that will give you local 2.3.3-SNAPSHOT versions. If you build with Maven, you can add those as dependencies. |
Looks like changes made in
ProviderBase
for 2.3 broke integration by RESTeasy, by removing call used by its jackson-based provider:https://github.com/resteasy/Resteasy/blob/e30b28d6cdd2cdfaaa90e94c471ae88d6b813bbe/jaxrs/providers/jackson2/src/main/java/org/jboss/resteasy/plugins/providers/jackson/ResteasyJackson2Provider.java#L107
as reported by @tbroyer.
Beyond fixing the immediate issue, it would be great if we could figure out a way to add tests for downstream dependencies, simple sanity checks to at least ensure that up-to-date versions compile with new Jackson JAX-RS provider implementations (and better yet, work to some degree). Something like this actually works with Jersey, since there are small tests we use for integration tests.
The text was updated successfully, but these errors were encountered: