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

    Struts Flow-How Struts Works?

    Struts Flow start with ActionServlet then call to process() method of RequestProcessor.

    Step 1. Load ActionServlet using load-on-startup and do the following tasks.

    Any struts web application contain the ActionServlet configuration in web.xml file.
    On load-on-startup the servlet container Instantiate the ActionServlet .
    First Task by ActionServlet : The ActionServlet takes the Struts Config file name as an init-param.
    At startup, in the init() method, the ActionServlet reads the Struts Config file and load into memory.
    Second Task by ActionServlet : If the user types http://localhost:8080/app/ in the browser URL bar, the URL will be intercepted and processed by the ActionServlet since the URL has a pattern *.do, with a suffix of "do". Because servlet-mapping is
    Third Task by ActionServlet : Then ActionServlet delegates the request handling to another class called RequestProcessor by invoking its process() method.


    Step 2. ActionServlet calls process() method of RequestProcessor.

    The RequestProcessor does the following in its process() method:
    a) The RequestProcessor looks up the configuration file for the URL pattern /submitForm (if the URL is http://localhost:8080/app/ and and finds the XML block (ActionMapping).

    ActionMapping from struts-config.xml

    <action path="/submitForm"
    <forward name="success"
    <forward name="failure" path="failure.jsp" />

    b) The RequestProcessor instantiates the EmpForm and puts it in appropriate scope either session or request.
    The RequestProcessor determines the appropriate scope by looking at the scope attribute in the same ActionMapping.
    c) RequestProcessor iterates through the HTTP request parameters and populates the EmpForm.
    d) the RequestProcessor checks for the validateattribute in the ActionMapping.
    If the validate is set to true, the RequestProcessor invokes the validate() method on the EmpForm instance.
    This is the method where you can put all the html form data validations.
    If Validate fail the RequestProcessor looks for the input attribute and return to JSP page mentioned in input tag.
    If Validate pass goto next step.
    e) The RequestProcessor instantiates the Action class specified in the ActionMapping (EmpAction) and invokes the execute() method on the EmpAction instance.

    signature of the execute method is

    public ActionForward execute(ActionMapping mapping,
    ActionForm form, HttpServletRequest request,
    HttpServletResponse response) throws Exception
    //your logic
    return mapping.findForward("success");

    f) In return mapping.findForward("success")
    RequestProcessor looks for the success attribute and forward to JSP page mentioned in success tag. i.e success.jsp.
    In return mapping.findForward("failure")
    RequestProcessor looks for the failure attribute and forward to JSP page mentioned in failure tag. i.e. failure.jsp

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