Hi everyone,
we are using Weld Dependency Injection in our Dropwizard services. I know that Weld is not officially supported, but maybe someone has a quick guess if there is any chance to fix the issues that I currently have after updating our services.
Some details:
- We Updated from Dropwizard 1.3.x to 2.0.x
- We are using weld-servlet-core v3.1.6.Final and jersey-cdi1x v2.33 which worked fine with Dropwizard 1.x
- META-INF/beans.xml contains bean-discovery-mode="all" (shouldn´t be the issue though anyway, because Weld version remained the same)
We get the following stacktrace:
org.jboss.weld.exceptions.IllegalArgumentException: WELD-001408: Unsatisfied dependencies for type <Service Name> with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject <internal service reference>
at <internal service reference>
at org.jboss.weld.manager.InjectionTargetFactoryImpl.createInjectionTarget(InjectionTargetFactoryImpl.java:83)
...
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type <Service Name> with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject <internal service reference>
at <internal service reference>
at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:378)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:290)
at org.jboss.weld.bootstrap.Validator.validateProducer(Validator.java:425)
...
Followed by
[main] ERROR io.dropwizard.cli.ServerCommand - Unable to start server, shutting down
javax.servlet.ServletException: jersey==io.dropwizard.jersey.setup.JerseyServletContainer@baa68670{jsp=null,order=-1,inst=true,async=true,src=EMBEDDED:null,STARTED}
Any help is appreciated, even if its just a statement that this is a known issue, but will not be supported in further releases.
Issue also posted here: https://github.com/dropwizard/dropwizard/issues/4055
Thanks a lot for any insights,
Bernhard