2 Replies Latest reply on Jun 20, 2003 10:19 AM by Harald Gliebe

    jdom.jar in jboss

    Mike Wazowski Newbie

      I`d like to include jdom.jar in jboss but got an error like

      12:20:43,453 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
      Cause: Incomplete Deployment listing:
      Packages waiting for a deployer: [org.jboss.deployment.DeploymentInfo@98a7bb0c { url=file:/J:/jboss-3.0.4_tomcat-4.1.12/server/default/lib/jdom.jar }
      deployer: null
      status: null
      state: INIT_WAITING_DEPLOYER
      watch: file:/J:/jboss-3.0.4_tomcat-4.1.12/server/default/lib/jdom.jar
      lastDeployed: 1056104436828
      lastModified: 1056104728000
      mbeans:

      there is also missing an "appropriate depoyer" when jdom.jar is placed in jboss\server\default\lib directory

      what do i need to do to use jdom classes within beans (jboss)

      thx mike

        • 1. Re: jdom.jar in jboss
          Jon Barnett Master

          I tried putting the jdom.jar that comes with JBoss 3.2.0 in the topmost lib directory of JBoss 3.0.6 and the server started without any errors during the bootstrap process. Does that work for you? I can't guarantee that it will solve any problems in use.

          Also, the 3.2.x release already includes jdom.jar in the topmost lib directory ... if that is an option for you.

          • 2. Re: jdom.jar in jboss
            Harald Gliebe Novice

            Hi Mike,

            the jdom.jar contains a META-INF/info.xml for which JBoss can't find an appropriate deployer. This behaviour of the deployer is fixed in later versions of JBoss, if you want to stay with 3.0.4 you can simply remove the info.xml file form jdom.jar.

            Regards,
            Harald