1 Reply Latest reply on Nov 26, 2003 12:34 PM by abuayyub

    CMR Problem

    Stephen Jacobs Newbie

      Is there any problem with setting up CMR between objects in different ejb-jar.xml files? I have done 1:N and 1:1 many times within entities that are defined in the same ejb-jar.xml, but my current code won't deploy with two .jar files. I am trying to reuse some legacy .jar files and was trying to add a class in my new ejb-jar that references one in another file. It gives me the following error:

      17:16:37,875 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean ope
      ration 'checkIncompleteDeployments()'
      Cause: Incomplete Deployment listing:
      Packages waiting for a deployer:

      Incompletely deployed packages:

      MBeans waiting for classes:

      MBeans waiting for other MBeans:
      [ObjectName: jboss.j2ee:jndiName=local/Unit,service=EJB
      state: FAILED
      I Depend On:
      Depends On Me: org.jboss.deployment.DeploymentException: Entity: Policy not fou
      nd for relation: unit-policy]


      "Policy" is the bean that is in the other .jar file that I know is deployed already, so there is should be no problem with loading dependencies. I can unit test it and see that Policy is there and working.

      Is it incorrect to create a CMR relationship that involves a class that isn't in your ejb-jar file? Is there some additional scoping I need to do in order to make this work?

      What am I doing wrong?

      Stephen J.