[richfaces-issues] [JBoss JIRA] (RF-11254) datascroller page not reset if datascroller not rendered, so data grid is empty

[u j (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/RF-11254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638437#comment-12638437 ] 

u j commented on RF-11254:
--------------------------

I tried version 4.1.0 M3 and the issue has disappeared.
The only thing I would change is the log level:

13:09:20,006 WARNING [org.richfaces.log.Components] (ajp-127.0.0.1-127.0.0.1-8009-5) Datascroller j_idt138:j_idt141: The requested page #2 isn't found in the model containing 1 pages. Paging is reset to page #1

Since it is a normal use case, I wouldn't issue a warning. IMHO, debug is sufficient.

Thanks
                
> datascroller page not reset if datascroller not rendered, so data grid is empty 
> --------------------------------------------------------------------------------
>
>                 Key: RF-11254
>                 URL: https://issues.jboss.org/browse/RF-11254
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.0.0.Final
>            Reporter: u j
>             Fix For: 4.2.0.Tracking
>
>
> RichFaces 4 resets correctly the current page to 1, if the model of the associated datagrid is reassigned,
> but this happens only if the rendered attribute of the datascroller is true.
> That is:
> - grid with > 1 page
> - set page 2 with datascroller
> - do some action which produces a new model with only 1 page
> - rendered attribute of datascroller is dynamic so it yields false if only one page (workaround because renderIfSinglePage does not work :-)
> -> data grid is empty instead of showing the content, because page is not reset to 1
> Binding the page attribute to a bean property and setting it to 1 doesn't help either.
> Code:
> <rich:dataScroller rendered="#{fn:length(bean.result) > 6}" />

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira