0 Replies Latest reply on Apr 15, 2014 9:38 AM by Péter Szűcs

    weld exception during deployment

    Péter Szűcs Newbie

      I'm working on a project that consists of several maven projects. Mine is a liferay portlet that depends several other projects. I'd like to deploy it on a JBoss application server, but when deploying I keep getting the following error:

       

       

       ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."biz.modit.tit.gop.education.teacherportlets.createtest-0.0.1-SNAPSHOT.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."biz.modit.tit.gop.education.teacherportlets.createtest-0.0.1-SNAPSHOT.war".WeldService: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [ListeningStatus] with qualifiers [@Default] at injection point [[field] @Inject private biz.modit.tit.gop.common.task.TaskComponentController.listeningStatus]
        at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]
        at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
      Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [ListeningStatus] with qualifiers [@Default] at injection point [[field] @Inject private biz.modit.tit.gop.common.task.TaskComponentController.listeningStatus]
        at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:311)
        at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:280)
        at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:143)
        at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:163)
        at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:382)
        at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:367)
        at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:379)
        at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83)
        at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
        ... 5 more
      

       

      I don't use weld directly, I depend on a project that uses it. I was told that this might be because there's a conflict between the cdi-portlet-bridge and something the other project uses, but removint the cdi-portlet-bridge dependency produced the same result. For project configuration I followed this tutorial. To be frank I've never used weld and I'm rather new to liferay as well so I'm a bit confused. Could you suggest something?