Labels:
example/sample code,
persistence
In the past, I had a few posts on how to implement pagination using displaytag(1, 2). That solution is feasible only with small result sets, the reason being that we will have the entire result set in memory (also called cache based paging). If the result set is large, then having the entire result set in memory will not be feasible. With large result sets, you cannot afford to have them in memory. In such case, you have to fetch a chunk of data at a time (query based paging). The down side of using query based paging, is that there will be multiple calls to the database for multiple page requests. In this post, I will describe how to implement simple query based caching solution, using Hibernate and a simple JSP. Time permitting, I will soon post a hybrid of cache based and query based paging example. Here is the code for implementing simple paging using a JSP and Hibernate:
- Download the latest version of hibernate from hibernate.org, and include all the required jars in your classpath.
- Hibernate configuration
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE hibernate-configuration PUBLIC
"-//Hibernate/Hibernate Configuration DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
<hibernate-configuration>
<session-factory>
<property name="connection.driver_class">oracle.jdbc.driver.OracleDriver</property>
<property name="connection.url">jdbc:oracle:thin:@localhost:1521/orcl</property>
<property name="connection.username">scott</property>
<property name="connection.password">tiger</property>
<property name="dialect">org.hibernate.dialect.Oracle9Dialect</property>
<property name="hibernate.current_session_context_class">thread</property>
<mapping resource="beans/Employee.hbm.xml" />
</session-factory>
</hibernate-configuration>hibernate.cfg.xml - The Employee bean class to hold the data
public class Employee {
public long empId;
public String empName;
public String empJob;
public long empSal;
public long getEmpId() {
return empId;
}
public void setEmpId(long empId) {
this.empId = empId;
}
public String getEmpJob() {
return empJob;
}
public void setEmpJob(String empJob) {
this.empJob = empJob;
}
public String getEmpName() {
return empName;
}
public void setEmpName(String empName) {
this.empName = empName;
}
public long getEmpSal() {
return empSal;
}
public void setEmpSal(long empSal) {
this.empSal = empSal;
}
}Employee.java - The Employee Mapping file: This listing of the Data Access Object uses the setMaxResults, and setFirstResult method of the Query object to extract the appropriate set of results for each page.
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<hibernate-mapping>
<class name="beans.Employee" table="Emp">
<id name="empId" column="EMPNO" type="long">
<generator class="native"/>
</id>
<property name="empName" column="ENAME" />
<property name="empJob" column="JOB" />
<property name="empSal" column="SAL" type="long"/>
</class>
</hibernate-mapping>Employee.hbm.xml - The Data Access Object
public class DAO {
private static int pageSize = 3;
public static List getData(int pageNumber) {
SessionFactory sessionFactory = new Configuration().configure().buildSessionFactory();
Session session = sessionFactory.getCurrentSession();
List result = null;
try {
session.beginTransaction();
Query query = session.createQuery("from Employee");
query = query.setFirstResult(pageSize * (pageNumber - 1));
query.setMaxResults(pageSize);
result = query.list();
session.getTransaction().commit();
} catch (Exception e) {
e.printStackTrace();
}
return result;
}
}DAO.java - The JSP
<jsp:root version="1.2" xmlns:jsp="http://java.sun.com/JSP/Page"
xmlns:c="urn:jsptld:http://java.sun.com/jsp/jstl/core">
<jsp:directive.page contentType="text/html; charset=UTF-8" />
<link rel="stylesheet" type="text/css" href="css/screen.css" />
<jsp:scriptlet>
int pageNumber=1;
if(request.getParameter("page") != null) {
session.setAttribute("page", request.getParameter("page"));
pageNumber = Integer.parseInt(request.getParameter("page"));
} else {
session.setAttribute("page", "1");
}
String nextPage = (pageNumber +1) + "";
session.setAttribute( "EmpList", data.DAO.getData(pageNumber));
System.out.println(((java.util.List)session.getAttribute("EmpList")).size());
String myUrl = "pagingEmp.jsp?page=" + nextPage;
System.out.println(myUrl);
pageContext.setAttribute("myUrl", myUrl);
</jsp:scriptlet>
<h2 align="center">Emp Table with Display tag</h2>
<jsp:useBean id="EmpList" scope="session" type="java.util.List"></jsp:useBean>
<table>
<tr>
<th>Employee Id</th>
<th>Name</th>
<th>Job</th>
<th>Salary</th>
</tr>
<c:forEach items="${EmpList}" var="emp" begin="0" end="10">
<tr>
<td><c:out value="${emp.empId}"></c:out></td>
<td><c:out value="${emp.empName}"></c:out></td>
<td><c:out value="${emp.empJob}"></c:out></td>
<td><c:out value="${emp.empSal}"></c:out></td>
</tr>
</c:forEach>
<tr>
<td colspan="2"></td>
<td colspan="2"><a href="${pageScope.myUrl}">nextPage</a></td>
</tr>
</table>
</jsp:root>pagingEmp.jsp
This JSP uses the DAO class to retrieve the Employee information from the database. The page number is passed as a parameter to the DAO. Notice that I did not implement the "previous" page, but it is similar to next. I assumed that we do not know the number of results for this example.

11 comments:
You wrote: "Time permitting, I will soon post a hybrid of cache based and query based paging example."
I would love to see this article. Perhaps, even if you don't get time to write the code, you could post some text explaining the design behind your solution?
Chris.
I was actually looking at this article today, and thinking if I can come up with any better idea paging in J2EE
Not sure if you have seen this http://blog.hibernate.org/cgi-bin/blosxom.cgi/2004/08/14#pagination
Hibernate blog explaining how to implement pagination using hibernate.
I think one question still remains is how do we display the total number of results as well.
Once we implemented paging in Hibernate the same way, but we have found that using the setFirstResult function is not very fast on large tables. This is actually good for the first few pages. The database system scans the whole table from the beginning to the place you want to display. It is faster to have one column with sequential row numbers and an index on it. In some cases, if records are added only at the end or beginning - this is possible.
--
our consulting company
To Piotr: actually, this depends on implementation of JDBC driver. Oracle drivers do exactly as you said. I don't know if PG or MySQL drivers have the same behaviour. I believe MySQL works because it has a native "first/max" support (if you can do that with SQL, the driver should do the same).
actually i am interested in Jsp code which uses hibernate to store dta & retrieve...can u help me by posting related code.
Thanks in advance!
Sanjay Yadav
i have gone through your paging..it is really usefull...
Hey Abhi, i thought ur article was excellent and very informative!
Abhi - Thanks for posting this it was very helpful, but unfortunately I still can't get it to work on my end. I'm getting the following exception:
org.apache.jasper.JasperException: /common/pagingEmp.jsp(1,121) Could not add one or more tag libraries.
Can you please specify which taglibs you are using? and how can I implement them in my web app? (I'm using Tomcat v6.
Thanks for your help!
Abhi - I got it to work now!! please ignore my previous post. But I still have a favor to ask, can you please walk me through the logic to implement "previous page"?
Thanks,
Tamer
Hi,I am new to JSP and Hibernate. Can you please show an example on how to insert data into DB from JSP and how to view it from JSP.
Post a Comment