Return-Path: <Matt@pcmove.com>
Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-users@xml.apache.org
Received: (qmail 87678 invoked from network); 16 Aug 2000 19:56:57 -0000
Received: from unknown (HELO cruise.concentric.net) (216.112.132.199)
  by locus.apache.org with SMTP; 16 Aug 2000 19:56:57 -0000
Received: by CRUISE with Internet Mail Service (5.5.2650.21)
	id <Q43FFRQ8>; Wed, 16 Aug 2000 16:03:14 -0400
Message-ID: <DF3195197E10D4118D70009027DC5C7C18EF21@CRUISE>
From: Matt Coolidge <Matt@pcmove.com>
To: cocoon-users@xml.apache.org
Subject: Dynamic WAP problems
Date: Wed, 16 Aug 2000 16:03:08 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

Hi everyone. I'm writing a WAP application. Basically, my XSP talks to the
database and sticks the resulting DocumentFragment into the output. I can
write an XSL stylesheet to make a WAP deck, with a card for each row of
data. But it's FAR too big if I do it this way; and WAP phones error out on
it.

I need a way of paging thru that initial document, 9 or 10 (or less!) rows
per deck. But I dont want to have to do a full DB query each time i page,
and then filter out the unwanted rows from the XML, and then apply a
stylesheet to make WAP. and I cant just break up the document, bacause it's
created dynamically by my XSP page. There's gotta be a better way, right?

Thanks for ANY help,
Matt Coolidge