Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This will happen when you have 2 forms of which second form is re-rendered by sumbitting the first form. This way the JSF view state of the second form will be completely lost (you can determine it yourself by the absence of a hidden input field with the name <code>javax.faces.ViewState</code> in the Ajax response). Submitting the second form after being re-rendered by a submit of the first form would then visually have no effect. Without the view state JSF won't process the submit of the form. Only a new form (with the proper view state!) will come back in place and hence the second submit works.</p> <p>You need to finetune the <code>render</code> attribute that way that only the contents of the second form is re-rendered and not the whole form itself. </p> <p>E.g.</p> <pre class="lang-xml prettyprint-override"><code>&lt;h:form id="form1"&gt; &lt;h:panelGroup id="content"&gt; ... &lt;h:commandButton value="Submit"&gt; &lt;f:ajax execute="@form" render="@form :form2:content" /&gt; &lt;/h:commandButton&gt; &lt;/h:panelGroup&gt; &lt;/h:form&gt; &lt;h:form id="form2"&gt; &lt;h:panelGroup id="content"&gt; ... &lt;h:commandButton value="Submit"&gt; &lt;f:ajax execute="@form" render="@form :form1:content" /&gt; &lt;/h:commandButton&gt; &lt;/h:panelGroup&gt; &lt;/h:form&gt; </code></pre> <p>In your particular case, give the <code>&lt;h:panelGrid&gt;</code> of the first form and the <code>&lt;h:dataTable&gt;</code> of the second form a fixed <code>id</code> and re-render just that from the other form on.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload