-
Notifications
You must be signed in to change notification settings - Fork 33
It appears jersey2-guice-spi is either not present or in conflict with some other Jar #38
Comments
@xinranxiao yea it seems something is initializing Jersey before you do. Are you initializing jersey2-guice straight from the Secondly I'd look at the classpath and the order in which JARs are being loaded. The jersey2-guice-spi JAR is purposely called |
Came here from dropwizard-guice - also encountering what looks like the same issue. I'm seeing:
|
This issue hasn't seen a real update for over 2 years. Is this project currently dead/inactive? I'm seeing the same issue when trying to using dropwizard-guice and swagger2.0. Both use this automated way of discovering resources. |
Hello, the project is currently inactive. We don't have any Jersey 2 w/ Guice projects. |
I'm trying to use this package with Dropwizard and Guice, using the "complex example" code in the wiki of this repo. I'm currently getting this error when I start my application
It looks like this is related to this (#37)... I did some monkeypatching with
JerseyGuiceUtils.java
and printed out the names of the providers withinlookupSPI
:And I get:
Currently the code just takes the first one... however it looks like the second one is the right class. Would it be better to just loop over the providers and check all of them?
The text was updated successfully, but these errors were encountered: