incubator-adffaces-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benj Fayle" <>
Subject RE: table delete row and immediate="true"
Date Thu, 13 Jul 2006 23:46:26 GMT
I have done this many times using partial page rendering techniques.
There are two ways you can do it. I'm assuming you are deleting the row
in the table model.

Method 1:

Add partialSubmit="true" to your command button. Then add the following
line of code to your deleteAction method:


This assumes getValuesTable() returns the same component that you bound
your table to using binding="#{testTable.valuesTable}"

Method 2:
Change your command button to look like this:

          <af:commandButton id="deleteButton"
                            text=" Delete"

Change the table to look like:

<af:table value="#{testTable.valuesTableModel}" 

You will also need to change the method signature of the deleteAction

  public void deleteAction(ActionEvent action)  {

-----Original Message-----
From: David Brunette [] 
Sent: Wednesday, July 12, 2006 11:02 AM
Subject: af:table delete row and immediate="true"


     Hi everybody.  I am having a problem with deleting a row from an
<af:table /> when I have my command button specify immediate="true".


<af:table value="#{testTable.valuesTableModel}" var="test"


            <f:facet name="selection">

                        <af:tableSelectMany text="Select and">

                                    <af:commandButton text="Delete"
action="#{testTable.deleteAction}" immediate="true">






                        <f:facet name="header">

                                    <af:outputText value="Value" />


                        <af:inputText value="#{test}" />





     While looking for what I was doing wrong, I came across an old post
on the Oracle forums:


     It seems as though this is exactly the problem that I'm having.
The last post was from a while ago so I was wondering if the enhancement
request that was mention has been fulfilled, or if this is still a
problem.  And if it is still a problem, can anybody elaborate on the
comment in the post of "implementing the "rowKey" part of that API to be
something stable across inserts and deletes" (sorry if it is obvious...
I'm still getting myself familiar with the CollectionModel stuff)?





View raw message