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
  • SCWCD : JSP directives

    SCWCD 1.5 Exam Kit

    Write JSP code that uses the directives: (a) 'page' (with attributes 'import', 'session', 'contentType', and 'isELIgnored'), (b) 'include', and (c) 'taglib'.

    page Directive with import attribute.

    Lets you specify the packages that should be imported by the servlet into which the JSP page gets translated. Generates import statements at top of servlet definition.

    Default imports: java.lang.*; javax.servlet.*; javax.servlet.jsp.*; javax.servlet.http.*.

    <%@ page import="package.class" %>
    or multiple classes/packages (separated by comma, NOT semicolon).
    <%@ page import="package.classA, package.classB, other.package.*" %>

    page Directive with session attribute.

    Controls whether or not page participates in HTTP sessions. Indicates that session (of type HttpSession) should be bound to existing session.

    false value means NO sessions will be used automatically. Attempts to access session variable by servlet will cause RUN-TIME failure.

    By default, it IS part of a session. All related pages have to do this for it to be useful.

    <%@ page session="true" %> <%-- default !!! --%>
    <%@ page session="false" %>

    page Directive with contentType attribute.

    Specify the MIME type of the page generated by the servlet that results from the JSP page. Attribute value cannot be computed at request time.

    <%@ page contentType="MIME-Type" %>
    <%@ page contentType="MIME-Type; charset=Character-Set" %>
    it is the same as (scriptlet):
    <% response.setContentType("MIME-Type; charset=Character-Set"); %>

    Note, you CANNOT use the contentType attribute for conditional run-time task. The following ALWAYS results in the Excel MIME type (page directive is evaluated only once during translation phase, and not during execution phase):

    <% boolean usingExcel = checkUserRequest(request); %>
    <% if (usingExcel) { %>
    	<%@ page contentType="application/" %>
    <% } %>
    the following approach should be used instead :
    <% boolean usingExcel = checkUserRequest(request); %>
    <% if (usingExcel) { %>
    	<% response.setContentType("application/"); %>
    <% } %>

    page Directive with isELIgnored attribute.

    The attribute is used to control whether the JSP 2.0 Expression Language (EL) is ignored (true) or evaluated normally (false).

    EL expressions will be ignored by default in JSP 1.2 applications. When upgrading a web application to JSP 2.0, EL expressions WILL BE INTERPRETED by default. The escape sequence '$' can be used to escape EL expressions that should not be interpreted by the container. Alternatively, the isELIgnored page directive attribute, or the <el-ignored> configuration element can be used to deactivate EL for entire translation units.

    <%@ page isELIgnored="false" %> <!-- default for JSP 2.0 -->
    <%@ page isELIgnored="true" %> <!-- default for JSP 1.2 -->

    include Directive.

    Lets you insert a file into servlet class at time the JSP file is translated into servlet. Should be placed in document at point where you want file inserted.

    The include directive lets you reuse navigation bars, tables, and other elements in multiple pages. The include directive includes a file in a JSP document at DOCUMENT TRANSLATION TIME. Included file can contain JSP code. Inclusion is recursive: included files may include files.

    	<title>Including Files at Translation Time (JSP)</title>
    	<%@ include file="somePage.jsp" %>

    taglib Directive.

    Can be used to define custom tags.

    <%@ taglib prefix="example" uri="" %>
    and web.xml:
    Notice the taglib-location specifies the location of the TLD. The taglib-uri is, for the most part, an arbitrary name given to the tag library. The name you give it can't conflict with other tag libraries in your deployment descriptor. In fact, adding the taglib element to the deployment descriptor is actually optional. You could instead reference the TLD directly in the taglib directive:
    <%@ taglib prefix="example" uri="/WEB-INF/example-taglib.tld" %>
    This isn't recommended because it reduces flexibility if you ever choose to rename or move the TLD. The uri would have to be changed in every JSP that used it.

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