a4j:support: action and reRender order problem

[pomcompot]

I got exactly the same problem than here with this code :

<h:form>
   <rich:extendedDataTable>
       […]
       <a4j:support  id="takeLivraisonSelection"
              event="onselectionchange"
               reRender="actionButtons"
               action="#{choixLivraison.takeLivraisonSelection}" />
   </rich:extendedDataTable>

  <div id="actionButtons">
      <s:button  view="/ChoixEnvironnement.xhtml"
              propagation="join"
               value="Sélectionner la cible du déploiement"
               disabled="#{choixLivraison.selectedLivraison}">
           <f:param name="from" value="ChoixLivraison" />
       </s:button>
  </div>
</h:form>

getSelectedLivraison is called before choixLivraison.takeLivraisonSelection, so selectedLivraison is empty and my button is never enabled. Don’t understand anything…  What can change the order of reRender and action phases?

Thanks in  advance.

P.S.: Sort of double posting because I don’t know if answered questions are followed.

[harut]

What is the scope of "choixLivraison" bean ???

[pomcompot]

Thanks for taking time for my problem.

Here the declaration of choixLivraisonBean:

@Stateful
@Name("choixLivraison")
@Scope(ScopeType.CONVERSATION) // Implicit with stateful
public class ChoixLivraisonBean implements ChoixLivraison {

     […]

}

[harut]

I think the problem is cause of wrong usage of Bean's scope...

Check this: http://www.packtpub.com/article/seam-conversation-management-using-jboss-seam-components-1

[nbelaevski]

Stephane,

Getters for such attributes as disabled can be called on earlier phases (e.g. 2nd or 3rd) in order to detect whether the component should be processed. If that's the problem, try wrapping rich:extendedDataTable into a4j:region, so that processing will be limited to components nested in region.