Scribd
Upload
4 views5 pages

Servlet Lifecycle Implementation Guide

The document outlines an academic exercise for a Computer Engineering course, focusing on the design and implementation of generic and HTTP servlets. It includes code examples for a basic servlet and a login cycle demonstration servlet, illustrating the servlet lifecycle with methods like init(), service(), and destroy(). The conclusion emphasizes the importance of the servlet lifecycle in handling client requests efficiently.

Uploaded by

wifeoftaehyungs
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
4 views5 pages

Servlet Lifecycle Implementation Guide

The document outlines an academic exercise for a Computer Engineering course, focusing on the design and implementation of generic and HTTP servlets. It includes code examples for a basic servlet and a login cycle demonstration servlet, illustrating the servlet lifecycle with methods like init(), service(), and destroy(). The conclusion emphasizes the importance of the servlet lifecycle in handling client requests efficiently.

Uploaded by

wifeoftaehyungs
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Department of Computer Engineering

Academic Year: 2025-26


Year: SE Semester: III Subject: JAVALab
Name of Student: Priyangee Kha
Roll No.: 31
Moodle Id: 24102108
Date of Performance: 1 9 - 9 - 2 5
Date of Submission: 19-9-25
Name of Instructor: Prof. Kadambari

EXPERIMENT NO. 4

Aim: Design and implement a generic servlet and an HTTP servlet.

Program:

<web-
app xmlns="[Link] xmlns:xsi="[Link]
-instance" xsi:schemaLocation="[Link]
[Link] version="5.0">
<servlet>
<servlet-name>LogincycleDemoservlet</servlet-name>
<servlet-class>LogincycleDemoservlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>LogincycleDemoservlet</servlet-name>
<url-pattern>/LogincycleDemoservlet</url-pattern>
</servlet-mapping>
</web-app>

import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];

public class FirstServlet extends GenericServlet {

public void service(ServletRequest req, ServletResponse resp) throws ServletException,


IOException {
[Link]("text/html");
PrintWriter pw = [Link]();

[Link]("<html>");
[Link]("<head><title>My first Servlet</title></head>");
[Link]("<body>");
[Link]("<h2>Welcome To Servlet World!</h2>");
[Link]("</body>");
[Link]("</html>");
[Link]();
}
}

Output:

EXERCISE1:

Program:

import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];

public class HelloServlet extends HttpServlet {

@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {

String userName = [Link]("name");

[Link]("text/html");
PrintWriter out = [Link]();

[Link]("<html>");
[Link]("<head><title>Greeting</title></head>");
[Link]("<body>");
[Link]("<h1>Hello, " + userName + "</h1>");
[Link]("</body>");
[Link]("</html>");
}
}
EXERCISE 2:

Program:
import [Link].*;
import [Link].*;
import [Link].*;

public class LogincycleDemoservlet extends HttpServlet {

private String message = "";

@Override
public void init() throws ServletException {
message += " init() called<br>";
[Link](" init() called");
}

@Override
protected void service(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
message += " service() called<br>";
[Link](" service() called");

[Link]("text/html");
PrintWriter out = [Link]();
[Link]("<h2>Hello from LogincycleDemoservlet</h2>");
[Link]("<p>" + message + "</p>");
}

@Override
public void destroy() {
[Link](" destroy() called");
}
}

Output:
Conclusion:

The code perfectly demonstrates the standard servlet lifecycle. The init() method handles one-time
initialization, while the service() method is responsible for processing each subsequent client
request, highlighting the fundamental "init once, serve many" principle of servlets.

You might also like