Tutorial Home
Hibernate
-
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
Struts
- 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
- 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
- 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
|
JSP Directives
There are two types of directive:
page :
The page directive define one or more of the following
case-sensitive attributes:
import="package.class" or
import="package.class1,...,package.classN".
This lets you specify what packages should be imported.
For example:
<%@ page import="java.util.*" %>
The import attribute is the only one that is allowed
to appear multiple times.
contentType="MIME-Type" or
contentType="MIME-Type; charset=Character-Set"
This specifies the MIME type of the output. The default
is text/html. For example, the directive
<%@ page contentType="text/plain" %>
has the same effect as the scriptlet
<% response.setContentType("text/plain"); %>
isThreadSafe="true|false". A value of
true (the default) indicates normal servlet processing,
where multiple requests can be processed simultaneously with a
single servlet instance, under the assumption
that the author synchronized access to instance variables.
A value of false indicates that the servlet should
implement SingleThreadModel, with requests either delivered
serially or with simultaneous requests being given separate
servlet instances.
session="true|false". A value of
true (the default) indicates that the predefined
variable session (of type HttpSession)
should be bound to the existing session if one exists,
otherwise a new session should be created and bound to it.
A value of false indicates that no sessions will be used,
and attempts to access the variable session will
result in errors at the time the JSP page is translated
into a servlet.
buffer="sizekb|none". This specifies the buffer
size for the JspWriter out.
The default is server-specific, but must be at least 8kb.
autoflush="true|false". A value of true,
the default, indicates that the buffer should be flushed
when it is full. A value of false, rarely used, indicates
that an exception should be thrown when the buffer overflows.
A value of false is illegal when also using
buffer="none".
extends="package.class". This indicates the superclass
of servlet that will be generated. Use this with extreme
caution, since the server may be using a custom superclass
already.
info="message". This defines a string that can
be retrieved via the getServletInfo method.
errorPage="url". This specifies a JSP page
that should process any Throwables thrown but not caught
in the current page.
isErrorPage="true|false". This indicates whether
or not the current page can act as the error page for
another JSP page. The default is false.
language="java". At some point, this is
intended to specify the underlying language being used.
For now, don't bother with this since java is both the
default and the only legal choice.
include :
This directive include files at the time the
JSP page is translated into a servlet. The directive looks like this:
<%@ include file="relative url" %>
The URL specified is normally interpreted relative to the JSP page that
refers to it, but, as with relative URLs in general, you can tell the system
to interpret the URL relative to the home directory of the Web server by
starting the URL with a forward slash. The contents of the
included file are parsed as regular JSP , and
thus can include static HTML, scripting elements, directives, and actions.
<%@ include file="header.jsp" %>
|
|