This content has been marked as final.
Show 2 replies
-
1. Re: WELD-001408 Unsatisfied dependencies for type
stevemaring Oct 7, 2011 12:30 PM (in response to stevemaring)I just tried dropping Weld into the war, via:
<dependency> <groupId>org.jboss.weld</groupId> <artifactId>weld-core</artifactId> <version>1.1.2.Final</version> <scope>runtime</scope> </dependency>
but that resulted in a deployment error of:
12:22:35,488 INFO [Version] WELD-000900 1.1.2 (Final) 12:22:35,504 ERROR [AbstractKernelController] Error installing to Instantiated: name=vfs:///C:/app/jboss-6.1.0.Final/server/default/deploy/gentiva-lifesmart-ela-assist-web-0.0.1-SNAPSHOT.war_WeldBootstrapBean state=Described: java.lang.IllegalArgumentException : Wrong arguments. new for target java.lang.reflect.Constructor expected=[org.jboss.weld.bootstrap.api.Bootstrap, org.jboss.weld.integration.deployer.env.bda.DeploymentImpl] actual=[org.jboss.weld.bootstrap.WeldBootstrap, org.jboss.weld.integration.deployer.env.bda.DeploymentImpl]
-
2. Re: WELD-001408 Unsatisfied dependencies for type
guidbona.guidbona.yahoo.com Oct 12, 2011 11:09 AM (in response to stevemaring)Hi Steve. First of all, do not add weld, cdi-api, etc to the deployment if you are deploying to JBoss: this will cause problems, instead of solving them.
You say that WorkerNameDAO is in the classpath, but is it in CDI module?
If it is inside a jar in WEB-INF/lib, make sure that that jar is a CDI module, that is, that beans.xml is present in META-INF. This is a common mistake.