problem in deployment in 4.0.4 GA due to mutual dependecy be

[amitguz]

I migrate my application from jboss 4.0.4 RC1 to JBOSS 4.0.4 GA
and I got error during the deployment.

In general the error is about mutual dependecy .
i.e - suppose I have 2 Stateless session bean:
1.) XXBean 2.)YYBean
and I have the following code:

@Remote ({XX.class})
public @Stateless class XXBean implements XX {

@EJB YYBean ybean;
}

@Remote ({YY.class})
public @Stateless class YYBean implements YY {

@EJB XXBean ybean;
}

this code in 4.0.4 GA will raise error during the depolyment process.
Does anybody know why? and how to overcome it?

thanks, amit

p.s - this is the error I got

--- MBeans waiting for other MBeans ---
ObjectName: jboss.j2ee:ear=testApp.ear,jar=testLogic.jar,name=XXBean,service=EJB3
State: NOTYETINSTALLED
I Depend On:
jboss.j2ee:ear=testApp.ear,jar=testLogic.jar,name=YYBean,service=EJB3
Depends On Me:
jboss.j2ee:ear=testApp.ear,jar=testLogic.jar,name=YYBean,service=EJB3

ObjectName: jboss.j2ee:ear=testApp.ear,jar=testLogic.jar,name=YYBean,service=EJB3
State: NOTYETINSTALLED
I Depend On:
jboss.j2ee:ear=testApp.ear,jar=testLogic.jar,name=XXBean,service=EJB3
Depends On Me:
jboss.j2ee:ear=testApp.ear,jar=testLogic.jar,name=XXBean,service=EJB3

[amitguz]

Is it a bug in the injection mechanism?

[pesalomo]

I have the same problem... This has worked in all earlier versions of EJB3 at least since summer 2005...

Is it wrong to use mutual dependencies?

Peter

[amitguz]

it's seem like a new bug in the injection code which inserted during the the new release of JBOSS (jboss 4.0.4 GA version).
however you can use look up directly instead of injection in the places you have the problem with mutual dependecy.