4 Replies Latest reply on Sep 11, 2003 5:57 PM by jonlee

    JBoss and Axis 1.1

    xmlviking

      Hello,

      I'm a complete novice when it comes to JBoss and well I have been out of the EJB space for hmm....2 years..LOL

      I'm trying to expose my Stateless Session beans to Axis 1.1. I have went through a couple tutorials but they seem to assume everythign works.

      1) Created my EJB's (Home, Bean, Local)
      2) Created my ejb-jar.xml file
      3) Created a myjar.jar folder in the deployment directory in JBoss...Server....Default....Deployment dir.

      Added the tags in the config-wsdd in Axis.

      Started JBoss...

      I can see the WebService in Axis and I can even get at the WSDL. But when I try to invoke a serivice JBoss throws the "Binding Context" error message.

      I seem to be seing in some places where people are coding an init() section into thier Session Beans. Do I need to do this? Or is this simply an object loader method?

      Thansk for any and all help...

      Sincerely,

      XMLViking

        • 1. Re: JBoss and Axis 1.1
          xmlviking

          OK the actuall error during boot strap is ..
          ---------------------------------------------------------------------
          [MainDeployer] Deployed package: file:/G:/DOWNLOADS/JAVA/JBos
          s/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/management/
          09:58:44,404 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean ope
          ration 'checkIncompleteDeployments()'
          Cause: Incomplete Deployment listing:
          Packages waiting for a deployer:

          Incompletely deployed packages:
          [org.jboss.deployment.DeploymentInfo@2dbab96c { url=file:/G:/DOWNLOADS/JAVA/JBos
          s/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/MyEJB.jar/ }
          deployer: org.jboss.ejb.EJBDeployer@f2225f
          status: Deployment FAILED reason: Verification of Enterprise Beans failed, see
          above for error messages.
          state: FAILED
          watch: file:/G:/DOWNLOADS/JAVA/JBoss/jboss-3.2.1_tomcat-4.1.24/server/default/
          deploy/MyEJB.jar/META-INF/ejb-jar.xml
          lastDeployed: 1063040317670
          lastModified: 1063013257062
          mbeans:
          ]MBeans waiting for classes:

          MBeans waiting for other MBeans:


          09:58:44,404 INFO [URLDeploymentScanner] Started
          ----------------------------- etc......-----------------------------

          • 2. Re: JBoss and Axis 1.1
            jonlee

            We need the error messages that occurred when MyEJB.jar was deployed. These final messages are just a summary set of held up deployments.

            • 3. Re: JBoss and Axis 1.1
              xmlviking

              Where might I get those?

              I mean all I can see is what's coming out of the cmd prompt. Is there a log file somewhere?

              Or should I be using some Jboss management tool to deploy my EJB's into the default/deploy directory?

              Thanks!

              • 4. Re: JBoss and Axis 1.1
                jonlee

                Usually, the operational errors are spilled to server.log. These are controlled by conf/log4j.xml. You'll see error message configurations for both your console and server.log.