1 Reply Latest reply on Mar 23, 2012 7:31 AM by Michael Heinen

    rich:tree inside a datalist not working in combination with ajax because row information is lost (version 4.2)

    Michael Heinen Newbie

      I use a datalist in order to iterate over some groups.

      The groups can be expanded or collapsed via a a4j:commandLink which re-renders only the current row of the datalist.

      The items of a group are rendered as radios, checkboxes or trees.


      Unfortunaltey (only) the trees are not working with richfaces 4.2 in combination with ajax commands.

      The tree is re-rendered via the ajax commandlink but it's value attribute is not resolved correctly.

      The value attribute of the tree refers to the var attribute of the outer datalist and this attribute is not valid anymore and points to the first row always!


      Simplified structure:

      <t:dataList id="groups"



        <h:panelGroup rendered="#{empty asGroup.parent}">

          <!--command expands/collaps a group-->

          <a4j:commandLink actionListener="#{MyDataController.toggleGroup}"




            <f:param name="dispTax" value="#{asGroup.name}"/>



          <t:div id="atBox">

           <h:panelGroup rendered="#{asGroup.open and (asGroup.type=='selectOneRadio' || asGroup.type=='selectManyCheckbox')}"> 



           <h:panelGroup rendered="#{asGroup.open and asGroup.type=='tree'}">


               <a4j:region id="arATTaxTree">

                 <rich:tree id="treeATItems"





      The tree does also not work if I rerender the complete outher list (groups)!

      However the tree is shown correctly if I reload the complete page via a non ajax command!       



      With richfaces 3.3.3 it worked with an ajaxListener of type ForceRender:

          <a4j:commandLink ajaxSingle="true"



            <a4j:actionparam name="foo"



                             actionListener="#{MyDataController.toggleGroup}" />

            <a4j:ajaxListener type="org.ajax4jsf.ajax.ForceRender"/>



      Question: Is there any important attribute of the rich:tree which solves this issue or is this simply a bug?