Updateable (CRUD) JSF Table - Button Enabling in ADF BC

Question

Hellow everyone,
The scene:
An updateable (CRUD) JSF table with "Create", "Commit", "Rollback" buttons.
By default, this buttons have the "Disabled" property binded to something like #{!bindings.Commit.enabled}
When page is rendered for the first time, the create button is enabled and the Commit and Rollback are disabled.
This two buttons get enabled if I insert a row in the table but not if I change data in a row.
So, I tried to do force the enablement of the buttons by:
1. Setting autosubmit = true for the inputText components in the table columns. (Tried it, no change)
2. Created a ChangeListener method in the pages backing bean and asigned it to the ValueChangeListener property of the inputText components. The method is:
public void valueChanged(ValueChangeEvent event) {
this.getSaveBtn().setDisabled(false); // saveBtn == Commit
As I expected, it didn't work. The buttons state must be saved in a some kind of persistence. In other products you use to save this kind of states in a session or request bean. But looking at the standard binding used by JDeveloper (#{!bindings.Commit.enabled} I deduce that this kind of persistence is used in a different way.
Unfortunatelly I didn't find information about the subject in JDevs documentation nor this forum.
The question:
Does anyone knows how can I learn to use this "bindigs" object used by JDev or how to use this kind of temporary peristence in JDev? I presume I can just forget all about it and use a session bean to manage all temporary persistence of this kind but I'd like to do it in JDevs way.
Thanks a lot for any help.
AG

Answer 1

If you don't care about the buttons themselves providing a visual cue that data has changed, then the easiest thing is to just remove the disabled property - then it will default to false and the button will always be enabled.
i.e., change this:
<af:commandButton actionListener="#{bindings.Commit.execute}" text="Commit"
  disabled="#{!bindings.Commit.enabled}"/>to this:
<af:commandButton actionListener="#{bindings.Commit.execute}" text="Commit"/>If you do need the buttons to be visual cues I would suggest setting the partial triggers property on the button to point to the table. (Although I haven't tried it in this case - I've never worked with an editable adf table before...)