[
https://issues.apache.org/jira/browse/TAP5-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203298#comment-16203298
]
Hudson commented on TAP5-2589:
------------------------------
FAILURE: Integrated in Jenkins build tapestry-trunk-freestyle #1648 (See
[https://builds.apache.org/job/tapestry-trunk-freestyle/1648/])
TAP5-2589: extend interface with methods that ease incremental paging
(jochen.kemnade: rev 4958b713fff229c6b0f028a7226a719549cf4d5b)
* (edit)
tapestry-core/src/main/java/org/apache/tapestry5/internal/grid/CollectionGridDataSource.java
* (edit)
tapestry-core/src/main/java/org/apache/tapestry5/grid/GridDataSource.java
TAP5-2589: improve data source handling if the pager is not shown
(jochen.kemnade: rev 68303b1d61d09c997bade870587d4586625f17a6)
* (edit)
tapestry-core/src/main/java/org/apache/tapestry5/corelib/components/GridRows.java
* (edit)
tapestry-core/src/main/resources/org/apache/tapestry5/corelib/components/Grid.tml
* (edit)
tapestry-core/src/main/java/org/apache/tapestry5/corelib/components/Grid.java
> Improve Grid implementation for "slow" data sources
> ---------------------------------------------------
>
> Key: TAP5-2589
> URL: https://issues.apache.org/jira/browse/TAP5-2589
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Jochen Kemnade
> Fix For: 5.5.0
>
>
> When using a Grid that's backed by a data source for which performing a count
> is expensive, performance is quite bad.
> There are some places where Grid (and subcomponents) call
> {{getAvailableRows()}} to determine whether the data source is empty or has
> (at least) a specific number of results. We should provide (and use) more
> specific and efficient methods in {{GridDataSource}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
