CODEWITHSUNDEEP
jbossguicejboss-weldwildflywildfly-8
David Limkys
David Limkys

Reputation: 5123

Jboss as7 to WildFly migration weld unsatisfied dependencies for type

I'm trying to migrate a jboss as 7 application to WildFly. For some reason I am getting the weld unsatisfied dependencies for type Set.

For just about every class that uses the @Inject (Using guice). I can not think of any way for solving this and have been stuck for several hours now.

Exception 0:
org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type 'classNameHere' with qualifires @Default 
at injection point [BackedAnnotatedField] @Inject cant.tell.du.services.data.syly.nbp.syll.gkfsn
at cant.tell.du.services.data.syly.nbp.syll.gkfsn(syll.java:0)

at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProbloms(Validator.java:368)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:289)
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:135)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:166)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:514)

Upvotes: 0

Views: 973

Answers (1)

shillner
shillner

Reputation: 1846

Ok, now I got the point that you are using guice instead of cdi. You could try to exclude the weld subsystem from your deployment like so:

<exclude-subsystems>
    <subsystem name="weld" />
</exclude-subsystems>

This should disable CDI for your deployment and you should not run into the same problems anymore.

Upvotes: 2

Related Questions