[richfaces-issues] [JBoss JIRA] Resolved: (RF-10860) Richfaces 4 rich:dataScroller pages facet not working as expected

Ilya Shaikovsky (JIRA) jira-events at lists.jboss.org
Mon Apr 11 06:56:35 EDT 2011


     [ https://issues.jboss.org/browse/RF-10860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ilya Shaikovsky resolved RF-10860.
----------------------------------

    Resolution: Duplicate Issue


> Richfaces 4 rich:dataScroller pages facet not working as expected
> -----------------------------------------------------------------
>
>                 Key: RF-10860
>                 URL: https://issues.jboss.org/browse/RF-10860
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.0.0.Final
>         Environment: Ubuntu 10.04, Eclipse 3.6, Jboss 5.1.0 GA
>            Reporter: Nikhil Patil
>
> We have a rich:dataTable and a rich:dataScroller for the datatable. The rich:dataScroller uses a "pages" facet.
> <rich:dataTable
>                      rows="2"                   
>                      value="#{userBean.itemsModel}" 
>                      var="item">
>                          <rich:column>
>                          #{item.label}
>                          </rich:column>
>                          <rich:column>
>                      #{item.value}
>                          </rich:column>
>                     <f:facet name="footer">
>                     <rich:dataScroller pageIndexVar="pageIndex" pagesVar="pages">
>                         <f:facet name="pages">
>                            <h:outputText value="#{pageIndex} / #{pages}" />
>                         </f:facet>
>                     </rich:dataScroller>
>                </f:facet>                   
> </rich:dataTable>
> The Pages facet for dataScroller does not produce the desired output (i.e. 1/3 etc.), instead it renders the default.
> NB : Sorry I couldn't decide whether this is a bug or a future request. Registering it as a bug for now since the expected behavior is mentioned in the documentation. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the richfaces-issues mailing list