Here are my two cents.
EJB Tier
Model the paged items as Entity Beans
The entity beans have a findBy method that allows them to searched for as
needed.
In EJB 1.1 the Entity bean's home object can return a Collection of
PrimaryKey
classes in response to a findBy call.
Model the list as a Stateful Session Bean.
In the Create call you would.
1) Get a reference to the home object for the item bean.
2) Use a finder method on the home object to get a collection of primary key
classes. Store the collection in a variable in the session bean.
3) Create a business method that returns a Vector of regular JavaBeans
similar
to below.
public Vector getPartOfList(int startAt, int numberOfElements)
This item uses the cached primary key list to build a Vector containing
regular
JavaBean "Value" objects from the data stored in the Entity Beans.
Web Tier
Create a JavaBean that encapsulates the logic of connecting to the Stateful
Session Bean and that exposes an Iterator that the JSP can use to interate
thru
the current subset of the list. Save this object in the Session scope of the
JSP environment.
Create JSPs that use an iteration tag library to show the next n results of
the
search
Advantages:
1) You can use the results of a single query over and over with a lazy
loading
mechanism.
2) Might scale better than a pure JSP/servlet approach.
Disadvantages:
1) Can a user in the same session have multiple indpendent lists?
2) Complexity
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
