 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Struts - A MVC web framework | | Tomcat - JSP/Servlet container | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | | JSP - A mailing list about Java Server Pages specification and reference | |
Struts & Hibernate
|
|
|
| | | Page by Page Iterator | Page by Page Iterator 2003-11-20 - By Koala Gnu
Back
Hi all,
Some questions regarding the page by page iterator pattern.
I learnt how this patterns works looking at the petstore application.
Then I tried to search on google a full description of this pattern, but
I found only one document in spanish.
First question. Can anyone of you send me a link with a full description
of this pattern?
Second question.
I have a DAO layer which perform a specific JDBC query Q that returns a
set of data of
type T.
Now I want display this result page by page. If I use the Page by Page
Iterator pattern, the query Q will be executed each time the user switch
from a page to another (each time the
start point of the cursor in the Resultset will change). But this is not
acceptable if the query is very expansive.
I read a thread on theserverside.com but I do not understand what to do
in this case.
I think that the Page by Page Iterator is not appropriate in this case.
Third Question. Is it possible combine the Page by Page solution with
another pattern that is more appropriate for complex queries? In this
way the client know that the result is paged
but it do not know how this paging is implemented (Page by Page or other
patterns).
Thanks in advance for any help.
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859 (See http://ISO-8859.ora-code.com)-1">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Hi all,<br>
<br>
Some questions regarding the page by page iterator pattern.<br>
<br>
I learnt how this patterns works looking at the petstore application.
Then I tried to search on google a full description of this pattern,
but I found only one document in spanish.<br>
<br>
<b>First question.</b> Can anyone of you send me a link with a full
description of this pattern?<br>
<br>
<b>Second question.</b><br>
<br>
I have a DAO layer which perform a specific JDBC query Q that returns a
set of data of <br>
type T.<br>
Now I want display this result page by page. If I use the Page by Page
Iterator pattern, the query Q will be executed each time the user
switch from a page to another (each time the<br>
start point of the cursor in the Resultset will change). But this is
not acceptable if the query is very expansive.<br>
<br>
I read a thread on theserverside.com but I do not understand what to do
in this case. <br>
I think that the Page by Page Iterator is not appropriate in this case.<b><br>
<br>
Third Question.</b> Is it possible combine the Page by Page solution
with another pattern that is more appropriate for complex queries? In
this way the client know that the result is paged<br>
but it do not know how this paging is implemented (Page by Page or
other patterns).<br>
<br>
Thanks in advance for any help.
</body>
</html>
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
|
