rich:dataTable with h:commandButton and jboss EL
gjeudy May 5, 2008 5:26 PMHi, i'm using Seam 2.0.1 with richfaces 3.2.0. I am listing data using rich:dataTable with nested h:commandButton inside. The behavior of this seems unspecified, for example I click on a button at position 10 and I get the id value of position 23 merged with the string values of position 10? (data corruption). I have verified in debug mode and the backing data is not corrupted.
I still haven't found a way to reproduce the issue in a consistent way. Heres my sample.
<h:form id="releasePackageItemForm">
<h:outputText value="No Items to display"
rendered="#{empty relPkg.refReleasePackageItems}" />
<rich:dataTable var="releasePackageItem"
value="#{relPkg.refReleasePackageItems}"
rendered="#{not empty relPkg.refReleasePackageItems}">
<rich:column sortBy="#{releasePackageItem.referenceDomain.domainName}" sortOrder="ASCENDING">
<f:facet name="header">
<h:outputText value="Domain name" />
</f:facet>
<h:outputText
value="#{releasePackageItem.referenceDomain.domainName}" />
</rich:column>
<rich:column sortBy="#{releasePackageItem.referenceDomain.domainDescription}">
<f:facet name="header">
<h:outputText value="Description" />
</f:facet>
<h:outputText id="description" value="#{releasePackageItem.referenceDomain.domainDescription}" />
</rich:column>
<rich:column sortBy="#{releasePackageItem.referenceDomain.typeCode}">
<f:facet name="header">
<h:outputText value="Type Code" />
</f:facet>
<h:outputText id="typeCode" value="#{releasePackageItem.referenceDomain.typeCode}" />
</rich:column>
<rich:column>
<f:facet name="header">
<h:outputText value="Actions" />
</f:facet>
<h:commandButton
action="#{domInstanceAdminAction.manageDomainInstances(releasePackageItem.referenceDomain)}"
value="Manage Domain Instances" />
</rich:column>
</rich:dataTable>
</h:form>Is there any reported incompatibilities with the elements im using ? I consider upgrading h:form to a4j:form and h:commandButton to a4j:commandButton even though I don't need ajax functionality just to see if that can get rid of the problem.
This problem only started to appear after upgrading to h:dataTable, h:column to their rich: counterparts.