Skip to main content

JSP - General

HTML comment that is sent to the client but not displayed by the browser.
<!-- Blah -->

Developer comment that is not sent to the client
<%-- Blah --%>

Expression that is evaluated and sent to the client each time the page is requested:
<%= Java Value %>
Current time: <%= new java.util.Date() %>
Your hostname: <%= request.getRemoteHost() %>

Statement or statements that are executed each time the page is requested:
<% Java Statement %>

String queryData = request.getQueryString();
out.println("Attached GET data: " + queryData);

Field or method that becomes part of class definition when page is translated into a servlet:

<%! Field Definition %>
<%! Method Definition %>

private int accessCount = 0;
private String randomHeading() {
return("<H2>" + Math.random() + "</H2>");

Directive: A JSP directive affects the overall structure of the servlet that results from the JSP page.  There are three main types of directives: page , include and taglib.

<%@ directive att="val" %>
<%@ page import="package.class1,...,package.classN" %>
is <  import="package.class1,...,package.classN" />

<%@ page contentType="application/" %>
<%@ page contentType="someMimeType; charset=someCharacterSet" %>

e.g. (excel.jsp)
First Last Email Address
Marty Hall
Larry Brown
Steve Balmer
Scott McNealy
<%@ page contentType="application/" %>
<%-- There are tabs, not spaces, between columns. --%>

<%@ page session="true" %> <%-- Default --%>

<%@ page isErrorPage="true" %>
<%@ page isErrorPage="false" %> <%-- Default --%>

Include: JSP has three main capabilities for including external pieces into a JSP document:
. the jsp:include action: lets you include the output of a page at request time

<jsp:include page="/fragments/StandardHeading.jsp">
<jsp:param name="bgColor" value="YELLOW" />

.the include directive: lets you insert jsp code into the main page before that main page is translated into a servlet.
<%@ include file="Relative URL" %> is
<jsp:directive.include file="..." />

.the jsp:plugin action: used to insert applets that use tha java plug-in into JSP pages.

<jsp:plugin type="applet"
width="475" height="350">
<jsp:param name="PARAM1" value="VALUE1" />
<jsp:param name="PARAM2" value="VALUE2" />

Shorthand JSP expression
${ EL Expression }

Invocation of custom tag


predefined Variables:
.request, the HttpServletRequest
.response, the HttpServletResponse
.session, the HttpSession associated with the request
. out, the Write(a buffered version of type JspWriter) used to send output to the client
.application, the ServletContext. This is a data structure shared by all servlets and JSP pages in the Web application and is good for storing shared data.
.config: This variable is the servletconfig object for this page. In principle, you can use it to read initialization parameters.
.pagecontext: JSP introduced a class Called Pagecontext to give a single point to access to many of the page attributes. The PageContext class has methods getRequest,getResponse,getOut,getSession, and so forth.
.page, This variable is simply a synonym for this and is not very useful.


Popular posts from this blog

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold highlighted in example below) which resolve the problems.   example:
<band height="20" splitType="Stretch"> <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/> …

JasperReports - Configuration Reference

Spring - Operations with jdbcTemplate

This class manages all the database communication and exception handling using a java.sql.Connection that is obtained from the provided DataSource. JdbcTemplate is a stateless and threadsafe class and you can safely instantiate a single instance to be used for each DAO.

Use of Callback Methods
JdbcTemplate is based on a template style of programming common to many other parts of Spring. Some method calls are handled entirely by the JdbcTemplate, while others require the calling class to provide callback methods that contain the implementation for parts of the JDBC workflow. This is another form of Inversion of Control. Your application code hands over the responsibility of managing the database access to the template class. The template class in turn calls back to your application code when it needs some detail processing filled in. These callback methods are allowed to throw a java.sql.SQLException, since the framework will be able to catch this exception and use its built-in excepti…