Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-2782

TCK test with inner class fails to generate exception

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • 6.0.0.Beta1
    • WildFly integration
    • None
    • Hide
      1. Download wildfly
      2. unzip into /tmp and set JBOSS_HOME env to /tmp/wildfly-31.0.1.Final
      1. git clone https://github.com/jakartaredhat/cdi-tck
      2. cd cdi-tck
      3. git checkout 4.1.x
      4. mvn -Drelease install
      5. dist-build/target/cdi-tck-4.1.0-SNAPSHOT/weld/jboss-as
      6. cd dist-build/target/cdi-tck-4.1.0-SNAPSHOT/weld/jboss-tck-runner
      7. mvn -Pupdate-jboss-as package
      8. mvn -Pupdate-jakarta-apis package
      9. mvn -Dtck package
      10. cd ../jboss-tck-runner
      11. mvn -Dincontainer -Dtest=
        org.jboss.cdi.tck.tests.invokers.invalid.ctor.ConstructorInvokerTest
         

       

      With this version of wildfly it looks like all invoker tests are failing due to class loading errors.

       

      Show
      Download wildfly unzip into /tmp and set JBOSS_HOME env to /tmp/wildfly-31.0.1.Final git clone https://github.com/jakartaredhat/cdi-tck cd cdi-tck git checkout 4.1.x mvn -Drelease install dist-build/target/cdi-tck-4.1.0-SNAPSHOT/weld/jboss-as cd dist-build/target/cdi-tck-4.1.0-SNAPSHOT/weld/jboss-tck-runner mvn -Pupdate-jboss-as package mvn -Pupdate-jakarta-apis package mvn -Dtck package cd ../jboss-tck-runner mvn -Dincontainer -Dtest= org.jboss.cdi.tck.tests.invokers.invalid.ctor.ConstructorInvokerTest     With this version of wildfly it looks like all invoker tests are failing due to class loading errors.  

      There are several invoker related tests that are expected to fail with 
      DeploymentException in the 4.1.0.Beta2 CDI TCK. An example of such a test is the org.jboss.cdi.tck.tests.invokers.invalid.ctor.ConstructorInvokerTest in the 4.1.x branch of the https://github.com/jakartaredhat/cdi-tck repo.
       
      When this test is run against wildfly-31.0.0.Final with the weld-6.0.0.Beta1, the following msg is seen:
       
      WELD-000900: 6.0.0 (Beta1)

      2024-02-29 03:18:24,495 INFO  [org.jboss.weld.Bootstrap] (Weld Thread Pool – 1) WELD-000119: Not generating any bean definitions from org.jboss.cdi.tck.tests.invokers.invalid.ctor.ConstructorInvokerTest$MyService because of underlying class loading error: Type org.jboss.cdi.tck.tests.invokers.invalid.ctor.ConstructorInvokerTest from [Module "deployment.ConstructorInvokerTest35162967636eea6857b4c0ace3be8bce6ffebd.war" from Service Module Loader] not found.  If this is unexpected, enable DEBUG logging to see the full error.

       

      but there are no deployment failures. This can be worked around by moving the 
      org.jboss.cdi.tck.tests.invokers.invalid.ctor.ConstructorInvokerTest$MyService inner class out of ConstructorInvokerTest, but this scenario should be causing a failure even if it is not for the correct reason.
       

      The full server.log is attached.
       
      server.log

        1. server.log
          23 kB

              Unassigned Unassigned
              rhn-engineering-sstark Scott Stark
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: