ADF Faces: Newbee problem with table

Question

Hello,
I try to generate a table like in the demo app:
<af:form>
<af:table allDetailsEnabled="true" var="row"
bandingInterval = "2"
banding = "row"
value="#{projectView.currentProjects}" rows="5">
<af:column sortable="true" sortProperty="proj_name">
<f:facet name="header">
<af:outputText value="#{bundle.proj_name}"/>
</f:facet>
<af:outputText value="#{row.proj_name}"/>
</af:column>
<af:column sortable="true" sortProperty="proj_descr">
<f:facet name="header">
<af:outputText value="#{bundle.proj_descr}"/>
</f:facet>
<af:outputText value="#{row.proj_descr}"/>
</af:column>
<f:facet name="detailStamp">
<af:panelGroup type="vertical">
<af:outputText value="Name: #{row.proj_name}"/>
<af:outputText value="Descr: #{row.proj_descr}"/>
<af:outputText value="Volume: #{row.proj_volume}"/>
<af:outputText value="Area: #{row.proj_area}"/>
</af:panelGroup>
</f:facet>
</af:table>
</af:form>
The currentProjects method returns a database query as a list of beans. The content of the beans is displayed. My problem is, when I click on e.g. 'Next' or 'All Details' nothing happens and I get javascript errors like this:
Error: _submitPartialChange is not defined
Source File: http://localhost:8080/timerec/faces/ADFbrowseProjects.jsp
Line: 25
I´m using EA 13. What am I doing wrong?
Thanks, Axel

Answer 1

The problem you're encountering is that the table view is being re-initialized whenever the underlying table model changes. Thus, the navigation appears to do nothing. The demo code doesn't "appear" to do anything special because the af:table value property is bound to a managed bean, periodicTable, that has session scope. Thus the table is built only once and the value binding is simply returning the same java object every time.
For you to accomplish the same thing, your code will need to return the SAME OBJECT (since I can't see the source code I don't really know if it's using object identity or equals()) each time unless your underlying data has actually changed.
I'm struggling with the same thing. I'm working with a small table and it's just easier to manage concurrency issues by pulling the data out of the database every time instead of building the logic to detect a change, but I'm having to build that due to this behavior.