Return-Path: Delivered-To: apmail-myfaces-users-archive@www.apache.org Received: (qmail 23482 invoked from network); 18 Jan 2009 17:07:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Jan 2009 17:07:49 -0000 Received: (qmail 43602 invoked by uid 500); 18 Jan 2009 17:07:46 -0000 Delivered-To: apmail-myfaces-users-archive@myfaces.apache.org Received: (qmail 43557 invoked by uid 500); 18 Jan 2009 17:07:46 -0000 Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Discussion" Delivered-To: mailing list users@myfaces.apache.org Received: (qmail 43548 invoked by uid 99); 18 Jan 2009 17:07:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Jan 2009 09:07:46 -0800 X-ASF-Spam-Status: No, hits=2.4 required=10.0 tests=HTML_MESSAGE,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of cagatay.civici@gmail.com designates 209.85.219.11 as permitted sender) Received: from [209.85.219.11] (HELO mail-ew0-f11.google.com) (209.85.219.11) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Jan 2009 17:07:38 +0000 Received: by ewy4 with SMTP id 4so169128ewy.12 for ; Sun, 18 Jan 2009 09:07:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=fauIvtcp9mFpqALY1Cmjg92Qbe8UEjswxQfPmZgjJmg=; b=g7mZtktFmgYfhRN1kpj9ypzqeGKgTEW5rXTox2EgKcrReiRX6337l7x86I2Vn22FXI LbBJpzNbIMDOS6A/bsksTpLnkDFM0c8MfI49oNa+/rOdoJ5da0xJyks4JkT8K/lakZWc jCBiLZxSm9Mi3+37wOBYD7E2cCgtwOyCqkP9g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=isdYb9Nnvrt6uGZxPoBcZ8dQGxK3silBW2iIdk+EHIohUkQow28RoTldn53Aj3xduq vFTWVf6D0kRazI0K/VwKpfjHU1ZfGDVZDT9nAzTwOoAPAaTIPw0MkjMzLKhFvq+broy7 o48oB1W+UbvI7AQ7z5z0quxfs0sA6jd8Ku2sw= Received: by 10.210.117.1 with SMTP id p1mr6051197ebc.180.1232298437000; Sun, 18 Jan 2009 09:07:17 -0800 (PST) Received: by 10.210.91.3 with HTTP; Sun, 18 Jan 2009 09:07:16 -0800 (PST) Message-ID: <8c9d4eaa0901180907i2f6d18b9ld5f723fccec1814d@mail.gmail.com> Date: Sun, 18 Jan 2009 17:07:16 +0000 From: "Cagatay Civici" To: "MyFaces Discussion" Subject: Re: How to Configure Search results using JSF/MyFaces In-Reply-To: <21530052.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_10899_18686706.1232298436990" References: <21530052.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_10899_18686706.1232298436990 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline This is not a UI thing and I think should be handled at data access rather than UI level. Hibernate api supports maxResult so you can limit the number of rows returned. On Sun, Jan 18, 2009 at 4:57 PM, bansi wrote: > > We use JSF 1.2, RichFaces 3.1, Spring 2.5, Hibernate 3.2 and have following > requirement > > "The maximum number of rows returned must be configurable so that users > don't query too much information." > > We are able to successfully implement search using RichFaces walk method of > Serializable data model which provides dataScroller for pagination > > Any pointers/suggestions will be greatly appreciated > > > -- > View this message in context: > http://www.nabble.com/How-to-Configure-Search-results-using-JSF-MyFaces-tp21530052p21530052.html > Sent from the MyFaces - Users mailing list archive at Nabble.com. > > ------=_Part_10899_18686706.1232298436990 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline This is not a UI thing and I think should be handled at data access rather than UI level.

Hibernate api supports maxResult so you can limit the number of rows returned.

On Sun, Jan 18, 2009 at 4:57 PM, bansi <mail2bansi@yahoo.com> wrote:

We use JSF 1.2, RichFaces 3.1, Spring 2.5, Hibernate 3.2 and have following
requirement

"The maximum number of rows returned must be configurable so that users
don't query too much information."

We are able to successfully implement search using RichFaces walk method of
Serializable data model which provides dataScroller for pagination

Any pointers/suggestions will be greatly appreciated


--
View this message in context: http://www.nabble.com/How-to-Configure-Search-results-using-JSF-MyFaces-tp21530052p21530052.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.


------=_Part_10899_18686706.1232298436990--