Also forgot to mention, that the grid component already has pagination that
is customizable + lazyloading, sorting etc.
http://tapestry.apache.org/current/tapestry-core/ref/org/apache/tapestry5/corelib/components/Grid.html
- Ville
--
View this message in context:
http://tapestry.1045711.n5.nab
Page has context, component has parameters.
Component should NOT care nor know the page it is in, to promote real
componentization. It is not the job of the component to decode the
parameters from web, the page should do that. And then the page should
forward the context as parameters to the compo
Thanks HLS , I appreciate the quick response. I have already implemented a
simple case and its working. I am reading the user guide to make sure that i
dont miss anything out.
Josh.
On Thu, Feb 24, 2011 at 11:46 PM, Howard Lewis Ship wrote:
> If you look at the source parameter of the Grid, it i
If you look at the source parameter of the Grid, it is a
GridDataSource object. You can bind a List to the source parameter,
and Tapestry takes care of converting the list to a GridDataSource,
but for large result sets from a database, you really want to use the
GridDataSource interface, because i
On Thu, 24 Feb 2011 17:16:27 -0300, Josh Kamau
wrote:
Thanks guys.
:)
I will implement the GridDataSource. I didnt know it existed.
It's in the Grid component reference as the type of the source parameter.
Thiago, for some personal reasons, i prefer using mybatis(formerly
ibatis)
a
Thanks guys.
I will implement the GridDataSource. I didnt know it existed.
Thiago, for some personal reasons, i prefer using mybatis(formerly ibatis)
as opposed to hibernate (i had a very bad experience with hibernate in a
live environment, most of it caused by my limited understanding of hiberna
On Thu, 24 Feb 2011 17:00:33 -0300, Howard Lewis Ship
wrote:
If you look at the source parameter of the Grid, it is a
GridDataSource object. You can bind a List to the source parameter,
and Tapestry takes care of converting the list to a GridDataSource,
but for large result sets from a datab
Also have a look at Tapestry's Hibernate integration [1] which supplies a
HibernateGridDataSource
[2] that implements pagination and only fetches the necessary objects from the
database.
Uli
[1] http://tapestry.apache.org/hibernate.html
[2]
http://tapestry.apache.org/tapestry5.2-dev/apidocs/org
If you look at the source parameter of the Grid, it is a
GridDataSource object. You can bind a List to the source parameter,
and Tapestry takes care of converting the list to a GridDataSource,
but for large result sets from a database, you really want to use the
GridDataSource interface, because i
