4 Replies Latest reply on Jul 4, 2011 7:43 AM by Carmen Teich

    Jboss 6Final: DEPLOYMENTS MISSING DEPENDENCIES

    Carmen Teich Newbie

      Hello, I make a migration from jboss 4.2.2 to jboss 6 final and when deploying my .ear-file I got this Error:

       

       

       

      Deployment "eDesk:service=ConversionJobService" is missing the following dependencies:

          Dependency "jboss.j2ee:module=beans.jar,service=EJB3" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.j2ee:module=beans.jar,service=EJB3' **")

       

      DEPLOYMENTS IN ERROR:

        Deployment "jboss.j2ee:module=beans.jar,service=EJB3" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.j2ee:module=beans.jar,service=EJB3' **

       

          at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1228) [:2.2.0.GA]

          at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:905) [:2.2.0.GA]

          at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:87) [:6.0.0.Final]

          at org.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.checkAllComplete(ProfileDeployerPluginRegistry.java:107) [:0.2.2]

          at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:135) [:6.0.0.Final]

          at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final]

          at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]

          at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]

          at java.lang.Thread.run(Thread.java:662) [:1.6.0_25]

       

       

      Please help me as soon as possible

        • 1. Re: Jboss 6Final: DEPLOYMENTS MISSING DEPENDENCIES
          Wolf-Dieter Fink Master

          Hoe do you start JBoss?

          Could it be that you remove parts of EJB3?

          • 2. Re: Jboss 6Final: DEPLOYMENTS MISSING DEPENDENCIES
            Carmen Teich Newbie

            I start the Jboss over the run.sh in the console. I have a new configuration for my tests. Its a copy of the default-configuration. I don't think that is anything missing. the structure is ok I think.

             

            At the moment I don't know what I should do! Please help!

            • 3. Re: Jboss 6Final: DEPLOYMENTS MISSING DEPENDENCIES
              jaikiran pai Master

              Do you have any <depends> or @Depends within your eDesk:service=ConversionJobService MBean? What does that *-service.xml file look like?

              • 4. Re: Jboss 6Final: DEPLOYMENTS MISSING DEPENDENCIES
                Carmen Teich Newbie

                The jboss-service.xml looks like this:

                 

                <?xml version="1.0" encoding="UTF-8"?>

                <!DOCTYPE server

                    PUBLIC "-//JBoss//DTD MBean Service 5.0//EN"

                    "http://www.jboss.org/j2ee/dtd/jboss-service_5_0.dtd">

                 

                <server>

                    <mbean code="de.xcom.xline.service.mbean.ConversionJobService" name="eDesk:service=ConversionJobService" xmbean-dd="">

                        <xmbean>

                            <description>

                                ConversionJobService

                            </description>

                            <class>de.xcom.xline.service.mbean.ConversionJobService</class>

                            <constructor>

                                <description>The no-arg constructor</description>

                                <name>de.xcom.xline.service.mbean.ConversionJobService</name>

                            </constructor>

                            <operation>

                                <description>restartConversionJobs

                                </description>

                                <name>restartConversionJobs</name>

                                <parameter>

                                    <description>refIds</description>

                                    <name>refIds</name>

                                    <type>java.lang.String</type>

                                </parameter>

                                <return-type>java.lang.String</return-type>

                            </operation>

                            <operation>

                                <description>restartOCRJobs

                                </description>

                                <name>restartOCRJobs</name>

                                <parameter>

                                    <description>refIds</description>

                                    <name>refIds</name>

                                    <type>java.lang.String</type>

                                </parameter>

                                <return-type>java.lang.String</return-type>

                            </operation>

                            <operation>

                                <description>getJobsForRefId

                                </description>

                                <name>getJobsForRefId</name>

                                <parameter>

                                    <description>refId</description>

                                    <name>refId</name>

                                    <type>java.lang.Long</type>

                                </parameter>

                                <return-type>java.lang.String</return-type>

                            </operation>

                            <operation>

                                <description>restartJob

                                </description>

                                <name>restartJob</name>

                                <parameter>

                                    <description>jobId</description>

                                    <name>jobId</name>

                                    <type>java.lang.Long</type>

                                </parameter>

                                <return-type>java.lang.String</return-type>

                            </operation>

                        </xmbean>

                        <depends>jboss.j2ee:module=beans.jar,service=EJB3</depends>

                    </mbean>

                </server>

                 

                 

                I found something like this: http://entjavastuff.blogspot.com/2010/07/migrating-to-jboss-51-from-jboss-42x.html

                 

                Did I have to change some packages on my code for the annotations like it is discribe on this page?

                 

                I only use the @LocalBinding or @RemoteBinding annotations. Should I do what is said on this page:

                 

                     "If you only use the @LocalBinding or @RemoteBinding annotations and you need a cross-platform alternative (well, at least across JBoss      platforms) that works all the way up to and including JBoss 6, then don't use the annotations. In stead, override the JNDI names using a      META-INF/jboss.xml file"

                 

                But when I change the import to: "import org.jboss.ejb3.annotation.LocalBinding;" Eclise could not revolve and I should configure the biuld path of my project.