Display tag pagination problem

Question

In display tag i used pagination feature ,when i want to see the list of 15 rows but display tag featch all the rows from database. every time when i click on pagination number,it featch all of the rows from db.bcoz of that it slow the performace of application.

I want that in display tag when i want to see the 15 rows then display tag also fetch 15 rows from db not entire db rows. Plz help me if some one knows.

Answer 1

You have to use external pagination feature. First, specify in html tag that you're using external pagination. And create an object implements org.displaytag.pagination.PaginatedList. Finally, you have to implement the DAO which makes actually query for 15 rows only and returns PaginatedList.

1) Your jsp will look like this

<display:table name="command" sort="external" partialList="true" size="${command.fullListSize}" pagesize="${command.objectsPerPage}">
  <display:column property="name" title="name"/>
  ...
</display:table>

Note that it specified the sort is external.

2) org.displaytag.pagination.PaginatedList implementation.

public class PaginatedListImpl<T> implements PaginatedList{
  private int fullListSize;
  private int objectsPerPage;
  private int pageNumber;
  private String searchId;
  private String sortCriterion;
  private SortOrderEnum sortDirection;
  private List<T> list;

//getters and setters
...
}

3) DAO Implementation sample using hibernate. You can do it with JDBC or anything but make sure you're making the right query to get 15 rows in proper order and return PaginatedListImpl object.

@SuppressWarnings("unchecked")
public PaginatedListImpl<T> getPaginatedList(PaginatedListImpl paginatedList) {
  int pageNum = paginatedList.getPageNumber();

  final int objectsPerPage = paginatedList.getObjectsPerPage();
  final int firstResult = objectsPerPage * pageNum;
  String sortOrderCriterion = pagiantedList.getSortOrderCriterion();
  String sortOrder = paginatedList.getSortOrder

  String className = type.getName().substring(type.getName().lastIndexOf(".") + 1);
  final StringBuilder fromClause = new StringBuilder("from " + className + " " + alias);
  String orderByClause = new StringBuilder(" order by ").append(sortCriterion).append(" ").append(sortDirection);

  final String hql = new StringBuilder().append(fromClause).append(orderClause).toString();
  List<T> resultList = getHibernateTemplate().executeFind(new HibernateCallback() {
  public Object doInHibernate(Session session) throws HibernateException, SQLException {
    return session.createQuery(hql)
      .setFirstResult(firstResult)
      .setMaxResults(objectsPerPage)
      .list();
    }
  });
  Long count = (Long)getHibernateTemplate().execute(new HibernateCallback() {           
    public Object doInHibernate(Session session) throws HibernateException, SQLException {
      return session.createQuery("select count(*) " +  fromClause).uniqueResult();
    }
  });
  paginatedList.setFullListSize(count.intValue());
  paginatedList.setList(resultList);
  paginatedList.setPageNumber(pageNum+1);
  paginatedList.setObjectsPerPage(objectsPerPage);
  return paginatedList;
}

Answer 2

Displaytag sends it’s pagination and sorting data using parameters that start with “d-”. So quick solution can be to check if request contains something starting with "d-",if yes then dont execute your query again.

Answer 3

For some reason using the PaginatedList didn't seem to work. I tried with the latest version and it seems there is some bug and it gives the error attribute size must be specified even if I hard code the size value. I went through other links/blogs and many people have pointed this out.

The option which I finally used is to store the data in the session. When the user clicks next it checks the data in session. If present, it will not hit the services layer. So far it has worked fine.