Hi All,

I'm using Hibernate 3.0.2 and wondering how people are handling pagination?

I have a typical n-tierd application using Struts/Tiles on the front end,
a set of Manager classes for BL (might convert into Stateless session beans), DAO classes for HQL and DB beans for persistence.

I'm using the ThreadLocal Session pattern.

My transactions are managed at the Manager class level.

I was thinking of using a DetachedQuery to implement pagination of a result set.

Is this a good idea? Is there a better/more common way of implementing this with Hibernate 3.0.2?

Thanks,
-Ben

I have basically the same question:

Pagination through different sessions

Can someone please help us with this small alteration of the common pagination pattern:

this.query = Hibernate.getSession().createFilter(order.items, "");
this.query.setMaxResults(Main.fetchSize);
results.fill(query.list());

/// ...
open new session
/// ...

Hibernate.getSession().lock(order,LockMode.NONE);// to reattach items too
this.query.setFirstResult(last).setMaxResults(Main.fetchSize);
results.fill(query.list());

throws Exception : The collection was unreferenced

How can we solve this? All comments are appreciated.

J'ai le meme probleme. Certains suggerent de garder l'object Query/Criteria du cote de Struts (ActionForm possiblement) et de le passer a la couche business. Cela dit je suis pas tout a fait satisfait a l'idee d'importer les classes Hibernate du cote de la couche presentation. Je me demande quel pattern d'autre utilisateurs auraient utiliser dans leur project? Une solution est de conserver les parametres de recherche et de reconstruire a chaque iteration la requete SQL, mais bon il doit y avoir une meilleur solution...