I tried new primefaces 3.0 M1 version jar and found following issue, which was not present in primefaces-3.0-SNAPSHOT.jar dated from 04.03.2010
I have many p:dateTable with filterBy columns inside of p:dataList.
Here the sample:
Code: Select all
<p:dataList value="#{applicationOperating.mapKeys}" var="targetKey">
<p:column>
<p:dataTable var="aPList" value="#{sessionScope.applicationOperating.getValueMap(targetKey)}" emptyMessage="No item found with given criteria">
<f:facet name="header" >
<p:panel header="Domain: #{targetKey.key} System: #{targetKey.unix} user: #{targetKey.value} " style="margin-top:10px;margin-bottom:10px">
<h:commandButton value="Close" style="float:right;" alt="Close" action="close"/>
</p:panel>
</f:facet>
<p:column headerText="Key" footerText="Key" filterMatchMode="contains" filterBy="#{aPList.key}" >
<h:outputText value="#{aPList.key}"/>
</p:column>
<p:column headerText="Value" footerText="Value" filterMatchMode="contains" filterBy="#{aPList.value}">
<h:outputText value="#{aPList.value}"/>
</p:column>
<p:column headerText="Access" footerText="Access">
<h:outputText value="#{aPList.access}"/>
</p:column>
</p:dataTable>
</p:column>
</p:dataList>
First problem is, filtering is not triggered by typing text in filter fields on first p:dateTable.
If I press Enter the page get reloaded an filtering start to work...
But behaviour has chenged.
With primefaces-3.0-SNAPSHOT.jar dated from 04.03.2010 filtering works as expected.
If I tipp text in filtering field for given column in p:dateTable, filtering is applied to this p:dateTable.
With primefaces 3.0 M1 If I tipp text in filtering field for given column in p:dateTable, filtering is applied no only to this p:dateTable. by also to all other p:dateTables... inside parent p:dataList.
This is of course also an interesting future which could be used... but is not what is expected.
Mabe you have some hints?