1 Reply Latest reply on Mar 24, 2010 6:56 AM by Aslak Knutsen

    Conversation injection broken with weld-se?

    Lincoln Baxter III Master

      So I'm trying to test some Conversation functionality, but having an issue:

       

      Add this to an examples/junit test case:

       

      /arquillian/trunk/examples/junit/src/test/java/com/acme/cdi/InjectionTestCase.java

       

         @Inject
         Conversation conversation;
      

       

      Then run it:

       

      mvn test -Pweld-embedded -Dtest=com.acme.cdi.InjectionTestCase
      

       

      You should get:

       

      WELD-001408 Injection point has unsatisfied dependencies.  Injection point:  field com.acme.cdi.InjectionTestCase.conversation;  Qualifiers:  [@javax.enterprise.inject.Default()]" type="org.jboss.weld.exceptions.DeploymentException">org.jboss.weld.exceptions.DeploymentException: WELD-001408 Injection point has unsatisfied dependencies.  Injection point:  field com.acme.cdi.InjectionTestCase.conversation;  Qualifiers:  [@javax.enterprise.inject.Default()]
          at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:276)
          at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:122)
          at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:141)
          at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:331)
          at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:317)
          at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:399)
          at org.jboss.arquillian.weld.WeldSEContainer.deploy(WeldSEContainer.java:102)
          at org.jboss.arquillian.impl.container.ContainerDeployer.deploy(ContainerDeployer.java:46)
          at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:100)
          at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
          at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:115)
          at org.junit.runners.ParentRunner.run(ParentRunner.java:220)
          at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
          at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
          at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
          at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:597)
          at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338)
          at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997)
      

       

      Any thoughts? Seems like a bug.