[
https://issues.jboss.org/browse/RF-13156?page=com.atlassian.jira.plugin.s...
]
Fabio Turizo commented on RF-13156:
-----------------------------------
Ok, having this tested with the 4.3.4 version the bug seems to be gone and the sorting
works as expected. In accordance to the roadmap when is this version expected to be
released?
Custom sorting on extended datatable not working.
-------------------------------------------------
Key: RF-13156
URL:
https://issues.jboss.org/browse/RF-13156
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.3.3
Environment: Oracle Glassfish 3.1.2 - JEE 6 Full Profile
Reporter: Fabio Turizo
Labels: extendedDataTable, sorting, waiting_on_user
Custom sorting on a extended datatable is not working well. With a extended data table
configured with this layout:
{code:xml}
<html
xmlns="http://www.w3.org/1999/xhtml"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:a4j="http://richfaces.org/a4j"
xmlns:rich="http://richfaces.org/rich">
<h:head>
<title>Titulo</title>
</h:head>
<h:body>
<h:form>
<h:panelGrid cellpadding="5" cellspacing="5"
columns="4" width="100%">
<f:facet name="footer">
<h:panelGrid cellspacing="10" columns="2"
width="80%">
<a4j:commandButton
actionListener="#{consultaFactibilidad.consultarDocumentos}"
execute="this"
render="documentos"
value="Buscar"
styleClass="boton"/>
</h:panelGrid>
</f:facet>
</h:panelGrid>
<rich:extendedDataTable var="documento"
value="#{consultaFactibilidad.documentos}"
id="documentos">
<rich:column id="formato" width="200px"
sortBy="#{documento.formato.nombreCalificado}"
sortType="custom"
sortOrder="#{controlOrdenTablas.orden}">
<f:facet name="header">
<a4j:commandLink execute="@this"
action="#{controlOrdenTablas.ordenar}"
render="documentos">
<h:outputLabel value="Formato" />
</a4j:commandLink>
</f:facet>
<h:outputText
value="#{documento.formato.nombreCalificado}"/>
</rich:column>
</rich:extendedDataTable>
</h:form>
</h:body>
</html>{code}
When the user clicks on the link for the only column on the table the table sorts
correctly ONLY the first time, the next click simply doesn't sort the data. No error
messages on the server log, no error messages on a a4j:log either. The next time stops
working completely. This only happens after the value collection is retrieved on the
action listener {code}#{consultaFactibilidad.consultarDocumentos}{code} is called. When
the data is retrieved before the page load, say on the postconstruct event listener on the
backing bean, then the sort works correctly all times. Finally this ONLY happens with the
extended datatable. It doesn't happen with a simple datatable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira