This content has been marked as final.
Show 8 replies
-
1. Re: Bug: Problem with pageIndex in rich:datascroller.
akira_ag Jun 19, 2007 2:20 PM (in response to akira_ag)My environment:
GlassFish v2
ajax4jsf 1.1
RichFaces 3.0.2
JDK 1.6 -
2. Re: Bug: Problem with pageIndex in rich:datascroller.
ilya_shaikovsky Jun 21, 2007 6:13 AM (in response to akira_ag)yes seems like dataScroller ignores this attribute. Will add a dug
-
4. Re: Bug: Problem with pageIndex in rich:datascroller.
akira_ag Jun 21, 2007 1:56 PM (in response to akira_ag)"ilya_shaikovsky" wrote:
http://jira.jboss.com/jira/browse/RF-341
Thanks again Ilya.
But I can hopes, what it and previous a bug (RF-258) will be fixed in the nearest releases? -
5. Re: Bug: Problem with pageIndex in rich:datascroller.
akira_ag Jun 21, 2007 1:59 PM (in response to akira_ag)"ilya_shaikovsky" wrote:
http://jira.jboss.com/jira/browse/RF-341
Hmmm...
???"RF-341" wrote:
pageIndex attribute should be removed from .tld
Remove setter and test
???
It's is a friendly and needed functionality for user. How it's removed?
:-(
How to change page index now? -
6. Re: Bug: Problem with pageIndex in rich:datascroller.
akira_ag Jun 22, 2007 8:37 PM (in response to akira_ag)Hi to All!
If anyone wanted to use a pageIndex-like functionality you can try a workaround -
create UIDatascroller and UIDataTable properties in your Managed Session Bean and pageIndex correctly save in user session.
It's work correctly. -
7. Re: Bug: Problem with pageIndex in rich:datascroller.
ilya_shaikovsky Jun 25, 2007 6:10 AM (in response to akira_ag)You may control the current page from dataTable side using "first" attribute.
-
8. Re: Bug: Problem with pageIndex in rich:datascroller.
doensen Jul 6, 2007 9:18 AM (in response to akira_ag)"ilya_shaikovsky" wrote:
You may control the current page from dataTable side using "first" attribute.
Hello,
I tried this out, but for me it doesn't work. My table is ajax-rendered, when a filter is beeing invoked. Both rich:dataTable and rich:dataScroller will be re-rendered when the response is coming back. Setting the attribute "first" of the rich:dataTable does not change the rich:dataScroller! The dataScroller stays at the last page, even if there is only one page to show. (the table seems empty!)
My work-around: implementing the filter as actionListener and parsing the component tree to find the dataScroller. The dataScroller has a function, which sets the first row to display (like dataTable does)// ... parsing the components tree until dataScroller element is found // ... HtmlDatascroller ds = (HtmlDatascroller) element; ds.setFirstRow(0);
I'm not sure if this is the best way, but it's working. Does someone have some other ideas, or am i to blind to see the simplest solution?
Greetings, Christophe Denis