Bi-directional dependency between two stateless session beans

[andy.miller]

I was updating an application that has many stateless session beans, and in adding some functionality, I have the following situation:

@Stateless

public class SupplierManagerBean implements SupplierManager {

     @EJB

     private ProductManager productManager;

...

@Stateless

public class ProductManagerBean implements ProductManager {

    @EJB

    private SupplierManager supplierManager;

...

So, this compiles just fine, but will not deploy cleanly.  The profile service says it fails, and says to look at previous errors of which there are none.  Then the in the summary of incomplete deployments you get an error about the state of the SupplierManagerBean, and that its missing a dependency on the ProductManagerBean, and of course the ProductManagerBean says its missing a dependency on the SupplierManagerBean.

So, its obvious that the deployer cannot handle this situation, but the question is should it be able to?  I cannot find information that says whether this is something that should be supported or not.

[jaikiran]

Cyclic injection of @EJB is a known problem with JBoss EJB3. You will have to add a @IgnoreDependency on either one side of the injection to get past this. Here's a thread which discusses the same issue http://community.jboss.org/message/366797

[andy.miller]

jaikiran wrote:

Cyclic injection of @EJB is a known problem with JBoss EJB3. You will have to add a @IgnoreDependency on either one side of the injection to get past this. Here's a thread which discusses the same issue http://community.jboss.org/message/366797

Thanks Jaikiran.  I'll make that change to the code.  As always, your help is greatly appreciated.

[wolfc]

Note that a cyclic dependency with two stateless beans should deploy just fine, because the real bean instance is only needed when the first invocation goes through.

I'm scheduling in https://jira.jboss.org/jira/browse/EJBTHREE-1074 to address this problem.

[andy.miller]

wolfc wrote:

Note that a cyclic dependency with two stateless beans should deploy just fine, because the real bean instance is only needed when the first invocation goes through.

I'm scheduling in https://jira.jboss.org/jira/browse/EJBTHREE-1074 to address this problem.

That's great.  The @IgnoreDependency did work for me in the mean time.