java - WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default -

i've reviewed other related questions on so, , haven't found answer question.

i upgrading jboss 7.11 wildfly 8.2 , have encountered people calling "infamous weld-001408" issue. however, situation seems different in not using @inject annotations, or should cause validation error far know.

the stack trace below seems indicate exception caused weld validator qualifier @default. make sense anyone?

i emphasize there neither @inject nor @default annotations in application anywhere. so, exception mysterious.

can point me in right direction application , running in wildfly 8.2?

if additional information needed, please ask , supply it, if possible.

thanks!!!

edit [12-may-2015]:

i wonder if has hibernate validator?

from pom.xml:

<dependency>   <groupid>org.hibernate</groupid>   <artifactid>hibernate-validator</artifactid>   <version>5.1.3.final</version>   <scope>runtime</scope> </dependency> 

am using hibernate validator correctly? there configuration needs supplied? there validator can used instead?

---

stack trace startup of wildfly:

11:21:57,196 error [org.jboss.msc.service.fail] (msc service thread 1-4) msc000001: failed start service jboss.deployment.unit."search.war".weldstartservice: org.jboss.msc.service.startexception in service jboss.deployment.unit."search.war".weldstartservice: failed start service         @ org.jboss.msc.service.servicecontrollerimpl$starttask.run(servicecontrollerimpl.java:1904) [jboss-msc-1.2.2.final.jar:1.2.2.final]         @ java.util.concurrent.threadpoolexecutor.runworker(threadpoolexecutor.java:1145) [rt.jar:1.7.0_21]         @ java.util.concurrent.threadpoolexecutor$worker.run(threadpoolexecutor.java:615) [rt.jar:1.7.0_21]         @ java.lang.thread.run(thread.java:722) [rt.jar:1.7.0_21]  caused by: org.jboss.weld.exceptions.deploymentexception: weld-001408:   ** unsatisfied dependencies type validator qualifiers @default   @ injection point [unbackedannotatedfield] @inject private ** org.hibernate.validator.internal.cdi.interceptor.validationinterceptor.validator   @ org.hibernate.validator.internal.cdi.interceptor.validationinterceptor.validator(validationinterceptor.java:0) weld-001475: following beans match type, none have matching qualifiers:   - validatorbean [id=org.hibernate.validator.internal.cdi.validatorbean_hv]          @ org.jboss.weld.bootstrap.validator.validateinjectionpointfordeploymentproblems(validator.java:372)         @ org.jboss.weld.bootstrap.validator.validateinjectionpoint(validator.java:293)         @ org.jboss.weld.bootstrap.validator.validateinterceptor(validator.java:569)         @ org.jboss.weld.bootstrap.concurrentvalidator$2.dowork(concurrentvalidator.java:85)         @ org.jboss.weld.bootstrap.concurrentvalidator$2.dowork(concurrentvalidator.java:83)         @ org.jboss.weld.executor.iterativeworkertaskfactory$1.call(iterativeworkertaskfactory.java:60)         @ org.jboss.weld.executor.iterativeworkertaskfactory$1.call(iterativeworkertaskfactory.java:53)         @ java.util.concurrent.futuretask$sync.innerrun(futuretask.java:334) [rt.jar:1.7.0_21]         @ java.util.concurrent.futuretask.run(futuretask.java:166) [rt.jar:1.7.0_21]         ... 3 more 

i had same problem on wildfly 9 after migration jboss eap 6.2! , workaround form https://issues.jboss.org/browse/wfly-2708 helped me. in active standalone.xml file weld subsystem configuration:

<subsystem xmlns="urn:jboss:domain:weld:2.0"/> 

add attribute require-bean-descriptor="true", like:

<subsystem xmlns="urn:jboss:domain:weld:2.0" require-bean-descriptor="true"/>