You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Mathias Broekelmann (JIRA)" <my...@incubator.apache.org> on 2005/07/28 11:16:24 UTC

[jira] Closed: (MYFACES-259) datatable, datascroller problem with mbean in session scope

     [ http://issues.apache.org/jira/browse/MYFACES-259?page=all ]
     
Mathias Broekelmann closed MYFACES-259:
---------------------------------------

    Resolution: Won't Fix

I see the problem but I donĀ“t see a way to solve it.

Try to set the first attribute of the datatable to a meaningfull value after you have changed the rowcount of your datamodel. Neither datatable nor datascroller are able to define what a meaningfull value is as it depends IMO on your business case.

> datatable, datascroller problem with mbean in session scope
> -----------------------------------------------------------
>
>          Key: MYFACES-259
>          URL: http://issues.apache.org/jira/browse/MYFACES-259
>      Project: MyFaces
>         Type: Bug
>     Versions: 1.0.9 beta
>     Reporter: Stephan
>     Assignee: Mathias Broekelmann
>  Attachments: DatatableTestBean.java, HitBean_snippet.java, dataScroller.jsp, hitlist_snippet.jsf, output.txt
>
> I have a MBean in session scope, which holds the data for the datatable. 
> The scroller for the table works fine, when I use it once or the rowCount of data never changes. But I get in trouble when I change the page of the scroller and change the rowCount.
> Example:
> 1. datatable has 100 rows, scroller shows 10 rows
> 2. I jump to page 5
> ... everything is fine
> After this the data changes ... the datatable has now 5 rows
> And now the problem comes out: The pageIndex of the scrollerComponent is still on page 5 ... and ... there is no data. When I jump to page 1 manually (by rewind-button) the data shows up on the first page.
> I tried all the examples with this combination and got allways the same situation. So, I think it could be a bug ...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira