Mailing-List: contact dev-help@beehive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Beehive Developers" <dev@beehive.apache.org>
Message-ID: <31593596.1157034262829.JavaMail.jira@brutus>
Date: Thu, 31 Aug 2006 07:24:22 -0700 (PDT)
From: "Eddie O'Neil (JIRA)" <dev@beehive.apache.org>
To: dev@beehive.apache.org
Subject: [jira] Resolved: (BEEHIVE-1102) implement partial data set support
 in the netui data grid
In-Reply-To: <966711.1145288957283.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/BEEHIVE-1102?page=all ]

Eddie O'Neil resolved BEEHIVE-1102.
-----------------------------------

    Fix Version/s: v.next
       Resolution: Fixed

SVN 431515 implements this feature and adds a "partialDataSet" flag to the configurePager tag; currently, this only supports rendering a data set of "page size" each time the data grid renders.  This could certainly be enhanced to support rendering a page from a partial data set containing 2+ pages of data -- just haven't gotten there yet.

The tests committed with the change provide examples of how this works.

> implement partial data set support in the netui data grid
> ---------------------------------------------------------
>
>                 Key: BEEHIVE-1102
>                 URL: http://issues.apache.org/jira/browse/BEEHIVE-1102
>             Project: Beehive
>          Issue Type: Improvement
>          Components: NetUI
>    Affects Versions: V1, 1.0.1, v.next
>            Reporter: Eddie O'Neil
>             Fix For: v.next
>
>
> The NetUI data grid supports rendering complete data sets, but it would be quite useful if the grid supported rendering partial / incomplete data sets.  This would allow webapp controller logic to fetch a smaller amount of data from a database or via an ORM framework like Hibernate or OpenJPA.  
> There are some changes needed in the data grid to support this -- specifically, the data grid needs to support:
>   - a partialDataSet attribute that forces the grid to start rendering data from the beginning of a data set rather than the middle
>   - support from the PagerModel to render the "current" item of data based on the value from a URL rather than from the location in the data set
>   - support from the data grid for finding the absolute "current" index in a data set rather than the relative "current" index in a partial data set.  This would allow updates to work correctly when a data grid or row is updating an item in a data set.

-- 
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