4 Replies Latest reply on Dec 11, 2009 6:48 AM by Dieter Steinwedel

    @Management leads with AOP into deployments errors

    Dieter Steinwedel Newbie


      I run in massive deployments errors on my project, because dependent classes are missing. I write a bean like this:

      @Service(objectName = "com.isios:service=Dummy")
      public class Dummy implements DummyMBean {


      Also I have this aop-xml in the META-INF directory:
      (I have replaced "<" and ">" with "{" and "}" otherwise the quote will be truncated)

      {?xml version="1.0" encoding="UTF-8"?}
      {aop xmlns="urn:jboss:aop-beans:1.0"}
      {typedef name="TD_Job" expr="class($instanceof{org.quartz.Job})" /}

      {aspect name="TimerJobAspect" class="com.isios.TimerJobAspect"/}

      {bind pointcut="execution(* $typedef{TD_Job}-}execute(..))"}
      {advice aspect="TimerJobAspect" name="setThreadContext" /}


      On deploying I get following output:

      Deployment "com.isios:service=Dummy" is missing the following dependencies:
      Dependency "<UNKNOWN com.isios:service=Dummy>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.j2ee:ear=myApp.ear,jar=dummy.jar,name=Dummy,service=EJB3' **")

      Deployment "<UNKNOWN com.isios:service=Dummy>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.j2ee:ear=myApp.ear,jar=dummy.jar,name=Dummy,service=EJB3' **

      But "com.isios:service=Dummy" is deployed! Is @Management missing the deployment happens without errors. Is the xml not deployed it also works with @Management. This happens with JBoss 5.1.0GA and 6.0.0.M1.

      What to do?