Skip to main content

JSP tutorial part 14:Difference Between Include Directive and Include action

Difference Between Include Directive and Include action

include Directive:
At JSP page translation time, the content of the file given in the include directive is ‘pasted’ as it is, in the place where the JSP include directive is used.
 Then the source JSP page is converted into a java servlet class.
The included file can be a static resource or a JSP page.
 Generally JSP include directive is used to include header banners and footers.
  The source JSP page gets compiled only if that page has changed.
  If there is a change in the included JSP file, the source JSP file will not be compiled and therefore the modification will not get reflected in the output.
Include Action:
<jsp:include page= "index.jsp“>
The jsp:include action element is like a function call. At runtime, the included file
will be ‘executed’ and the result content will be included with the source JSP page.
When the included JSP page is called, both the request and response objects are
passed as parameters.
If there is a need to pass additional parameters, then jsp:param element can be
used.
Note : If the resource is static, its content is inserted into the calling JSP file, since
there is no processing needed.
Invoking a Servlet from a JSP Page
As when invoking one JSP page from another, you can invoke a servlet from a
JSP page through the jsp:include and jsp:forward action tags.
·          Following is an example:
<jsp:include page="/servlet/MyServlet" flush="true" />
·          When the servlet has finished executing, control is transferred back to the JSP
page and the page continues executing.
·          The following statement clears the page buffer, terminates the execution of the
JSP page, and executes the servlet:
·          <jsp:forward page="/servlet/MyServlet" />
·
In reality, It is other way , i.e. A servlet that acts as a controller invokes JSP
Alternatively, you can pass data between a JSP page and a servlet through an appropriately scoped Java Bean or through attributes of the HTTP request object.
Calling a servlet from a JSP- html form action
<FORM METHOD="POST|GET" ACTION="application_URL/JSP_URL">
<!-- Other tags such as text boxes and buttons go here -->
</FORM>
Calling a servlet from a JSP – jsp:forward
Invoking a servlet from a JSP directly through the jsp:include or jsp:forward tags.
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Call the servlet through jsp:forward tag</title>
</head>
<body>
<p> Calling Servlet from JSP </p>
<jsp:forward page=“/JSPProject/CounterServlet"></jsp:forward>
</body>
Invoking a JSP from a JSP
To invoke a JSP file from another JSP file, you can perform one of the following:
•Specify the URL of the second JSP file on the FORM ACTION attribute:
<FORM action=“JSP_URL">
……
</FORM>
•Specify the URL of the second JSP file in an anchor tag HREF attribute:
<a href="JSP_URL"> reference-text </a>

•Using <jsp:forward > or <jsp:include> action tags.

Comments

Popular posts from this blog

OPERATION MANUAL FOR RS232 TO RS422/RS485 VICE-VERSA

INTRODUCTION: Milestone model LD-15U is a RS232,  to RS422/RS485 converter is designed for high-speed data transmission between computer system and or peripherals over Iong distance under high noise conditions. They provide dual line interface per signal. APPLICATIONS: Application for these converters can be for factory automation, Programmable logic controllers,, attendance recording systems, Barcode Readers, remote data transmission, remote terminals, EPABX etc. SPECIFICATIONS: Input: RS232-T×D, R×D, DSR (for control), GND (D9 Female connector) Output: RS422/RS485-Tx+, Tx-, Rx+. Rx-(D9 Male Connector). Each signal is protected by spike suppressor, fuse and has opto-isolation. Selection Switch: 1. Rear side has 2-way'SELECT' switch for selecting 2-Wire or 4-Wire mode in RS422/RS485 application. 2. (Optional) Rear side has 3-way'SELECT' switch for selecting AUTO Mode (No Handshake Signal), DSR+ Mode (+12V Control) and DSR-Model (-_12V Control) for co

Java Server page tutorial part 3: JSP Life Cycle

JSP Life Cycle: A JSP life cycle can be defined as the entire process from its creation till the destruction which is similar to a servlet life cycle with an additional step which is required to compile a JSP into servlet. Following are the steps followed by a JSP Container: ◦ Compilation  ◦ Parsing the JSP.  ◦ Turning the JSP into a servlet.  ◦ Compiling  the servlet.  ◦ Initialization ◦ Execution ◦ Cleanup Architecture: 1.       JSP Compilation: When a browser asks for a JSP, the JSP engine first checks to see whether it needs to compile the page.  If the page has never been compiled, or if the JSP has been modified since it was last compiled, the JSP engine compiles the page. The compilation process involves three steps: ◦ Parsing the JSP. ◦ Turning the JSP into a servlet.  ◦ Compiling the servlet.  2.       JSP Initialization: When a container loads a JSP it invokes the jspInit() method before servicing any requests.  If you need to perform

JSTL-JSP Standard Tag Library part 1

Evolution of JSTL: Java is a flexible, general-purpose programming language, JavaServer pages(JSP) depends on java but hides some of the hard details of writing full- fledged programs.  The JSP Standards Tag Library(JSTL) builds on top of JSP, making it even easier to use. Architecture : In this figure large web applications are designed using java, JSTL, and othe components like databases. In large applications, it's common for requests from web browser to be handled by a java program called a servlet, which interacts with databases and other Java code on the server. The servlet figures out how it wants a response be printed and then forwards the user to the right JSTL page, which takes care of nothing more than presenting information. As JSP grew in popularity, it became clear that different sites' custom tags fell into familiar, frequently used patterns.  For example, many pages needed to loop over data to print tables and lists. Vendors of JSP c