2 Replies Latest reply on Nov 23, 2007 8:21 AM by Ales Justin

    Deployers tests and EJB errors

    Ales Justin Master

      I'm currently running what is to be MC2_beta7 in current AS5 trunk code to tests its deployers suite.
      And I get a bunch of errors, where I really don't see what is for me to handle or what fails due to EJB3/metadata refactoring.

      Let me just list some of them. :-)

      Caused by: java.lang.RuntimeException: Error determining structure: testdeployers-ear1.ear
      Caused by: java.lang.RuntimeException: testdeployers-jbas4548-ds.xml module listed in application.xml does not exist within .ear testdeployers-ear1.ear
       at org.jboss.deployment.EARStructure.determineStructure(EARStructure.java:243)
       ... 59 more
      Caused by: java.io.FileNotFoundException: JarHandler@30287876[path= context=file:/C:/projects/jboss5/trunk/testsuite/output/lib/testdeployers-ear1.ear real=file:/C:/projects/jboss5/trunk/testsuite/output/lib/testdeployers-ear1.ear] has no child: testdeployers-jbas4548-ds.xml
      


      Getting this multiple times:
      *** DEPLOYMENTS IN ERROR: Name -> Error
      
      vfsfile:/C:/projects/jboss5/trunk/testsuite/output/lib/testdeployers-ear-noappxml.ear -> org.jboss.deployment.DeploymentException: entity class not found: JBAS4548_EntityPK
      
      
      *** CONTEXTS IN ERROR: Name -> Error
      
      vfsfile:/C:/projects/jboss5/trunk/testsuite/output/lib/testdeployers-ear-noappxml.ear -> org.jboss.deployment.DeploymentException: entity class not found: JBAS4548_EntityPK
      


      *** DEPLOYMENTS IN ERROR: Name -> Error
      
      vfsfile:/C:/projects/jboss5/trunk/testsuite/output/lib/testdeployers-jbas2904.ear -> org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/C:/projects/jboss5/trunk/testsuite/output/lib/testdeployers-jbas2904.ear
      
      
      *** CONTEXTS IN ERROR: Name -> Error
      
      vfsfile:/C:/projects/jboss5/trunk/testsuite/output/lib/testdeployers-jbas2904.ear -> org.xml.sax.SAXException: cvc-complex-type.2.4.b: The content of element 'application' is not complete. One of '{"http://java.sun.com/xml/ns/j2ee":display-name, "http://java.sun.com/xml/ns/j2ee":icon, "http://java.sun.com/xml/ns/j2ee":module}' is expected. @ *unknown*[11,15]
      



        • 1. Re: Deployers tests and EJB errors
          Adrian Brock Master

           

          "alesj" wrote:
          I'm currently running what is to be MC2_beta7 in current AS5 trunk code to tests its deployers suite.
          And I get a bunch of errors, where I really don't see what is for me to handle or what fails due to EJB3/metadata refactoring.

          Let me just list some of them. :-)

          Caused by: java.lang.RuntimeException: Error determining structure: testdeployers-ear1.ear
          Caused by: java.lang.RuntimeException: testdeployers-jbas4548-ds.xml module listed in application.xml does not exist within .ear testdeployers-ear1.ear
           at org.jboss.deployment.EARStructure.determineStructure(EARStructure.java:243)
           ... 59 more
          Caused by: java.io.FileNotFoundException: JarHandler@30287876[path= context=file:/C:/projects/jboss5/trunk/testsuite/output/lib/testdeployers-ear1.ear real=file:/C:/projects/jboss5/trunk/testsuite/output/lib/testdeployers-ear1.ear] has no child: testdeployers-jbas4548-ds.xml
          



          The error message is correct. There is no such file in the ear.
          Probably a badly ported test?


          Getting this multiple times:
          *** DEPLOYMENTS IN ERROR: Name -> Error
          
          vfsfile:/C:/projects/jboss5/trunk/testsuite/output/lib/testdeployers-ear-noappxml.ear -> org.jboss.deployment.DeploymentException: entity class not found: JBAS4548_EntityPK
          
          
          *** CONTEXTS IN ERROR: Name -> Error
          
          vfsfile:/C:/projects/jboss5/trunk/testsuite/output/lib/testdeployers-ear-noappxml.ear -> org.jboss.deployment.DeploymentException: entity class not found: JBAS4548_EntityPK
          



          The error message is misleading:
           public JDBCEntityMetaData(JDBCApplicationMetaData jdbcApplication,
           EntityMetaData entity)
           throws DeploymentException
           {
           this.jdbcApplication = jdbcApplication;
           entityName = entity.getEjbName();
           listCacheMax = 1000;
           fetchSize = 0;
          
           try
           {
           entityClass = getClassLoader().loadClass(entity.getEjbClass());
           }
           catch(ClassNotFoundException e)
           {
          // HERE: Prints the ejb-name instead of the missing class and no nested execption!
           throw new DeploymentException("entity class not found: " + entityName);
           }
          


          It is true that the enity class is not deployed in the ear.
          Another badly ported test?


          
          *** DEPLOYMENTS IN ERROR: Name -> Error
          
          vfsfile:/C:/projects/jboss5/trunk/testsuite/output/lib/testdeployers-jbas2904.ear -> org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/C:/projects/jboss5/trunk/testsuite/output/lib/testdeployers-jbas2904.ear
          
          
          *** CONTEXTS IN ERROR: Name -> Error
          
          vfsfile:/C:/projects/jboss5/trunk/testsuite/output/lib/testdeployers-jbas2904.ear -> org.xml.sax.SAXException: cvc-complex-type.2.4.b: The content of element 'application' is not complete. One of '{"http://java.sun.com/xml/ns/j2ee":display-name, "http://java.sun.com/xml/ns/j2ee":icon, "http://java.sun.com/xml/ns/j2ee":module}' is expected. @ *unknown*[11,15]
          



          This is also correct. You need at least one module to satisfy the schema.
          It worked before because we didn't validate application.xml

          • 2. Re: Deployers tests and EJB errors
            Ales Justin Master

             

            "adrian@jboss.org" wrote:

            Probably a badly ported test?
            ...
            Another badly ported test?

            I didn't port the tests.
            I just fixed how deployers work, and ran what was there already. :-)