in this direction. thanks for the hint. Then come the other requirements as well: - ability to render one record on more than one row - dynamic col-spans according to different data-objects - automatic datascroller - sort and filter headers (multiple sort criterias)
Our users (read the developers here) are VERY creative... But I still hope we find the cash to finance our inhous infrastructure project... to make such components ;-) regards Alexander -----Original Message----- From: Simon Kitching [mailto:[EMAIL PROTECTED] Sent: Friday, January 13, 2006 2:11 PM To: MyFaces Discussion Subject: RE: An optimised pattern for using t:dataTable - please verify. On Fri, 2006-01-13 at 13:34 +0100, Jesse Alexander (KBSA 21) wrote: > I am milling around since quite some time on the subject of > datatables. > > In our app we have the case that hibernates fetches a few megabytes of > data, which will then be saved in the state and the hibernate-objects > remain referenced -> no gc... > > My current thoughts are about a datamodel that does not keep all data > but just a part of the data active and requests the missing data when > paging is requested... > > But I still have the unfinished business of the optional validation for > JSF 1.1 (without facelets) > > if we find some developers that want to start on such a better table- > component... (without committer-rights) we can share the code on a > temporary base on the js-comp.sf.net project Have you read this? I'm using this with success, as are others: http://wiki.apache.org/myfaces/WorkingWithLargeTables Regards, Simon
