This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
Conflicts in importing duplicate classes from javax rs-api 2.1.1 and jsr311-api 1.1.1 #3451
Unanswered
pallavisantosh19
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm using the conductor client module to write a java application that posts StartWorkflowRequests to Conductor. The conductor-client module pulls in javax.ws.rs:javax.ws.rs-api:2.1.1 as a runtime dependency.
This introduces the following class not found exception
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.netflix.conductor.client.http.WorkflowClient]: Factory method 'conductorWorkflowClient' threw exception; nested exception is java.lang.NoClassDefFoundError: javax/ws/rs/core/NoContentException
Caused by: java.lang.NoClassDefFoundError: javax/ws/rs/core/NoContentException
Caused by: java.lang.ClassNotFoundException: javax.ws.rs.core.NoContentException
Providing javax.ws.rs:javax.ws.rs-api:2.1.1 as a compile time dependency introduces duplicate/different classes in the classpath added by javax.ws.rs:jsr311-api:1.1.1.
How are people handling this issue?
Excluding the jsr311-api introduces a number of class not found exceptions -
org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.netflix.conductor.client.http.WorkflowClient]: Factory method 'conductorWorkflowClient' threw exception; nested exception is java.lang.NoClassDefFoundError: Could not initialize class com.sun.jersey.core.header.MediaTypes
Beta Was this translation helpful? Give feedback.
All reactions