Are You Recruiter/Hiring Manager?
Cloud-based Candidate Screening | Online Tests
PMP 1600 Questions
PMP 1600 Questions
1600 PMP mock questions 1400 CAPM mock questions 800 SCJP 6 mock questions 600 OCAJP 7 mock questions 590 OCPJP 7 mock questions 556 SCWCD 5 mock questions 500 OCEJWCD 6 mock questions pdfDownload (java,struts, hibernet etc)

Tutorial Home


  • Advantage of Hibernate over JDBC
  • Hibernate Setup with an web Application
  • First Hibernate Application
  • Hibernate mapping with Database TABLE
  • Hibernate Data Type-Java Data Type - SQL Data Type mapping
  • One to Many Relation in Hibernate
  • One to Many Relation in Hibernate bi-directional
  • Many to Many Relation in Hibernate
  • HQL: The Hibernate Query Language
  • Criteria Queries
  • Criteria Queries : Equal (eq), Not Equal(ne), Less than (le), greater than (gt),greater than or equal(ge) and Ordering the results
  • Criteria Queries: And OR conditions
  • Hibernate generator to generate id (primary key)
  • prevent concurrent update in Hibernate,slate object updatation in Hibernate,version checking in Hibernate


  • Model View Controller (MVC)
  • Model View Controller (MVC)
  • Struts Flow-How Struts Works?
  • Struts Tutorial - Struts Setup- First Struts Action class setup
  • Message Resources
  • Validation Framework
  • Validation Framework-client side
  • ForwardAction
  • IncludeAction
  • DispatchAction
  • LookupDispatchAction
  • DynaActionForm
  • DynaActionForm
  • Struts Tutorial - Mutli-click prevention using struts tokens-Prevent Duplicate Submission
  • Logic Iterate Map and List


  • JSP Tutorial
  • Introduction to JSP
  • JSP Comments
  • JSP Syntax
  • JSP Scripting Elements :Scriptlet, expression, declaration
  • JSP Directives
  • implicit objects in JSP
  • JSP Actions
  • Introduction to JSP
  • jsp:useBean
  • The jsp:setProperty Action
  • The jsp:getProperty Action
  • Introduction to JSP


  • Spring Tutorial
  • Introduction to Spring
  • Benefits of Using Spring Framework
  • Inversion of Control in Spring
  • Introduction to BeanFactory
  • Dependency Injection in Spring
  • Collections Setter Injection
  • Bean Scopes in Spring
  • Spring IOC Setup Step by Step
  • Bean Lifecycle in Spring
  • ApplicationContext
  • MessageSources in Spring
  • Web Spring MVC framework
  • Developing Your First Spring Web Application
  • Developing Your Second Spring Web Application with Spring Form
  • Developing Your First Spring Web Application with Spring Validation Framework with Code Example
  • Spring integration with Hibernate
  • Struts Tutorial -- Code Examples


    DispatchAction is another useful built-in Struts Action.Use DispatchAction when a set of actions is closely related and separating them into multiple Actions would result in duplication of code. For example : If there are three operation like delete, activate, deactivate employee. You can create three different Actions ActivateEmpAction, DeleteEmpAction and DeActivateEmpAction. This is a valid approach, although not elegant since there might be duplication of code across the Actions since they are related. DispatchAction is the answer to this problem. With DispatchAction, you can combine all three Actions into one.

    Follow the below five steps to setup DispatchAction.

    Step 1. In the JSP page (empdetails.jsp)

    <%@ taglib uri="/WEB-INF/struts-tiles.tld" prefix="tiles" %>
    <%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html" %>
    <%@ taglib uri="/WEB-INF/struts-bean.tld" prefix="bean" %>
    <%@ taglib uri="/WEB-INF/struts-logic.tld" prefix="logic" %>
    <html:form action="/saveEmp" method="post">
    <html:link page="/emp/" />
    <html:link page="/emp/" />
    <html:link page="/emp/" />

    Step 2. Adding ActionForm Entry in struts-config.xml

    Add the following entry in the struts-config.xml file.

    <form-bean name="EmpForm"   

    Step 3. Add action mapping in the struts-config.xml file:

    Add the following action mapping in the struts-config.xml file:

    <action path="/empaction" type="com.techfaq.action.EmpAction"

        <forward name="delete-success" path="/jsp/deletesuccess.jsp"/>
        <forward name="activate-success" path="/jsp/activatesuccess.jsp"/>
        <forward name="deactivate-success" path="/jsp/deactivatesuccess.jsp"/>

    Step 4. In the Action class.

    public class EmpAction extends DispatchAction {
    public ActionForward activate(ActionMapping mapping,
    ActionForm form, HttpServletRequest request,
    HttpServletResponse response) throws Exception
    //your logic
    public ActionForward delete(ActionMapping mapping,
    ActionForm form, HttpServletRequest request,
    HttpServletResponse response) throws Exception
    //your logic
    } public ActionForward deactivate(ActionMapping mapping,
    ActionForm form, HttpServletRequest request,
    HttpServletResponse response) throws Exception
    { //your logic

    Step 5. In the EmpForm

    public class EmpForm extends ActionForm {
    int empId;
    String firstName;
    public String getFirstName() {
    return firstName;
    public void setFirstName(String firstName) {
    this.firstName = firstName;
    public int getEmpId() {
    return empId;
    public void setEmpId(int empId) {
    this.empId = empId;

    Now in the browser type http://localhost:8080/app/jsp/empdetails.jsp

    In the above example DispatchAction was used handle hyperlinks. DispatchAction is a good choice when there are form submissions using the regular buttons . Just name all the buttons same. <html:submit property="step">Delete</html:submit> <html:submit property="step">Activate</html:submit> <html:submit property="step">Deactivate</html:submit>

    The information you are posting should be related to java and ORACLE technology. Not political.