Problem in faces-config.xml cycle detection

Question

Hi,
I'm having the following problem in my jsf application. I have a loginMangager bean which holds a reference to the logged user and which is used by many other beans in my application. But in a particular situation I'm getting the following error:
SEVERE: JSF will be unable to create managed bean listaChecagemBean when it is requested.  The following problems where found:
     - Managed bean mesaTarefasBean contains cyclic references.  Evaluation path: mesaTarefasBean -> loginManager -> listaChecagemBean -> loginManager.My faces-config.xml looks like this:
  <managed-bean>
    <managed-bean-name>loginManager</managed-bean-name>
    <managed-bean-class>
      br.gov.pgfn.efdv.mesa.view.login.LoginManagerBean
    </managed-bean-class>
    <managed-bean-scope>session</managed-bean-scope>
  </managed-bean>
  <managed-bean>
    <managed-bean-name>listaChecagemBean</managed-bean-name>
    <managed-bean-class>
      br.gov.pgfn.efdv.mesa.view.ListaChecagemBean
    </managed-bean-class>
    <managed-bean-scope>session</managed-bean-scope>
    <managed-property>
      <property-name>loginManager</property-name>
      <value>#{loginManager}</value>
    </managed-property>
    <managed-property>
      <property-name>mesaTarefasBean</property-name>
      <value>#{mesaTarefasBean}</value>
    </managed-property>
    <managed-property>
      <property-name>listaChecagemFacade</property-name>
      <value>#{listaChecagemFacade}</value>
    </managed-property>
  </managed-bean>
  <managed-bean>
    <managed-bean-name>mesaTarefasBean</managed-bean-name>
    <managed-bean-class>br.gov.pgfn.efdv.mesa.view.MesaTarefasBean</managed-bean-class>
    <managed-bean-scope>session</managed-bean-scope>
    <managed-property>
      <property-name>loginManager</property-name>
      <value>#{loginManager}</value>
    </managed-property>
    <managed-property>
      <property-name>mesaTarefasFacade</property-name>
      <value>#{mesaTarefasFacade}</value>
    </managed-property>
  </managed-bean>As you can see, there is not really a cycle here since the loginManagerBean does not depend on any other bean. If you think of it as directed graph, listaChecagemBean is connected to mesaTarefasBean and both of them are connected to the loginManagerBean, which is not connected to any other bean, it's a sink node.
I'm a missing something? Is this a bug?
I'm using JSF 1.2 RI 1.2_05 and Tomcat 6.0.
Thanks in advance,
Andr� Rodrigues

Answer 1

Hi Ryan,
I still problems with the release 1.2_07 which works fine with 1.2_04 when I use external beans through a custom el-resolver.
<?xml version="1.0" encoding="UTF-8"?>
<faces-config xmlns="http://java.sun.com/xml/ns/javaee"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd"
     version="1.2">
     <application>
          <el-resolver>net.t_mobile.test.resolver.TestELResolver</el-resolver>
     </application>
     <managed-bean>
          <managed-bean-name>sessionBean</managed-bean-name>
          <managed-bean-class>net.t_mobile.test.beans.SessionBean</managed-bean-class>
          <managed-bean-scope>session</managed-bean-scope>
          <managed-property>
               <property-name>externalBean</property-name>
               <value>#{externalBean}</value>
          </managed-property>
     </managed-bean>
     <managed-bean>
          <managed-bean-name>dummyA</managed-bean-name>
          <managed-bean-class>net.t_mobile.test.beans.DummyBean</managed-bean-class>
          <managed-bean-scope>session</managed-bean-scope>
          <managed-property>
               <property-name>sessionBean</property-name>
               <value>#{sessionBean}</value>
          </managed-property>
     </managed-bean>
     <managed-bean>
          <managed-bean-name>dummyB</managed-bean-name>
          <managed-bean-class>net.t_mobile.test.beans.DummyBean</managed-bean-class>
          <managed-bean-scope>session</managed-bean-scope>
          <managed-property>
               <property-name>sessionBean</property-name>
               <value>#{sessionBean}</value>
          </managed-property>
          <managed-property>
               <property-name>parentBean</property-name>
               <value>#{dummyA}</value>
          </managed-property>
     </managed-bean>
</faces-config>
The dependencies are like follows:
dummyB.parentBean = dummyA
dummyB.sessionBean = sessionBean
dummyA.sessionBean = sessionBean
sessionBean.externalBean = externalBean (resolved through external el-resolver)
If I remove "dummyB" or the reference to externalBean no cycles are detected anymore.
Could you confirm this bug?
Regards,
Marc