Q1.

Attempt any three of the following: 15

a. Explain the architecture of Java Enterprise Application.

java EE Application Components
Java EE applications are made up of components. A Java EE component is a self-
contained functional software unit that is assembled into a Java EE application
with its related classes and files and communicates with other components. The
Java EE specification defines the following Java EE components:
• Application clients and applets are client components.
• Java Servlet and JavaServer Pages (JSP) technology components are web
components.
• Enterprise JavaBeans (EJB) components (enterprise beans) are business
components.
Java EE components are written in the Java programming language and
compiled in the same way as any Java programming language program.
The difference when you work with the Java EE platform, is Java EE
components are assembled into a Java EE application, verified that they
are well-formed and in compliance with the Java EE specification, and
deployed to production where they are run and managed by the Java EE
server.
Java EE Architecture
Normally, thin-client multitiered applications are hard to write because they
involve many lines of intricate code to handle transaction and state management,
multithreading, resource pooling, and other complex low-level details. The
component-based and platform-independent Java EE architecture makes Java EE
applications easy to write because business logic is organized into reusable
components and the Java EE server provides underlying services in the form of a
container for every component type. Because you do not have to develop these
services yourself, you are free to concentrate on solving the business problem at
hand.
Containers and Services
Component are installed in their containers during deployment and are the
interface between a component and the low-level platform-specific functionality
that supports the component. Before a web, enterprise bean, or application client
component can be executed, it must be assembled into a Java EE application and
deployed into its container.
The assembly process involves specifying container settings for each component
in the Java EE application and for the Java EE application itself. Container
settings customize the underlying support provided by the Java EE Server, which
include services such as security, transaction management, Java Naming and
Directory Interface (JNDI) lookups, and remote connectivity. Here are some of
the highlights:
• The Java EE security model lets you configure a web component or
enterprise bean so system resources are accessed only by authorized
users.
• The Java EE transaction model lets you specify relationships among
methods that make up a single transaction so all methods in one
transaction are treated as a single unit.
• JNDI lookup services provide a unified interface to multiple naming and
directory services in the enterprise so application components can access
naming and directory services.
• The Java EE remote connectivity model manages low-level
communications between clients and enterprise beans. After an enterprise
bean is created, a client invokes methods on it as if it were in the same
virtual machine.
The fact that the Java EE architecture provides configurable services means that
application components within the same Java EE application can behave
differently based on where they are deployed. For example, an enterprise bean
can have security settings that allow it a certain level of access to database data in
one production environment and another level of database access in another
production environment.
Container Types
The deployment process installs Java EE application components in the
following types of Java EE containers. The Java EE components and container
addressed in this tutorial are shown in Figure 5.
• An Enterprise JavaBeans (EJB) container manages the execution of all
enterprise beans for one Java EE application. Enterprise beans and their
container run on the Java EE server.
• A web container manages the execution of all JSP page and servlet
components for one Java EE application. Web components and their
container run on the Java EE server.
• An application client container manages the execution of all application
client components for one Java EE application. Application clients and
their container run on the client machine.
• An applet container is the web browser and Java Plug-in combination
running on the client machine.
b. Classify the EE Containers. Explain.
Java EE Containers
Normally, thin-client multitiered applications are hard to write because they
involve many lines of intricate code to handle transaction and state management,
multithreading, resource pooling, and other complex low-level details. The
component-based and platform-independent Java EE architecture makes Java EE
applications easy to write because business logic is organized into reusable
components. In addition, the Java EE server provides underlying services in the
form of a container for every component type. Because you do not have to
develop these services yourself, you are free to concentrate on solving the
business problem at hand.
Container Services
Containers are the interface between a component and the low-level platform-
specific functionality that supports the component. Before a web, enterprise bean,
or application client component can be executed, it must be assembled into a Java
EE module and deployed into its container.
The Java EE security model lets you configure a web component or enterprise
bean so that system resources are accessed only by authorized users.
• The Java EE transaction model lets you specify relationships among methods
that make up a single transaction so that all methods in one transaction are
treated as a single unit.
• JNDI lookup services provide a unified interface to multiple naming and
directory services in the enterprise so that application components can access
these services.
• The Java EE remote connectivity model manages low-level communications
between clients and enterprise beans. After an enterprise bean is created, a
client invokes methods on it as if it were in the same virtual machine.
Container Types
The deployment process installs Java EE application components in the Java EE
containers as illustrated in Figure 1-5.
Figure 1-5 Java EE Server and Containers
 • Java EE server: The runtime portion of a Java EE product. A Java EE server
provides EJB and web containers.
• Enterprise JavaBeans (EJB) container: Manages the execution of
enterprise beans for Java EE applications. Enterprise beans and their
container run on the Java EE server.
• Web container: Manages the execution of JSP page and servlet components
for Java EE applications. Web components and their container run on the
Java EE server.
• Application client container: Manages the execution of application client
components. Application clients and their container run on the client.
• Applet container: Manages the execution of applets. Consists of a web
browser and Java Plug-in running on the client together.
c. Write a short note on javax.servlet package
Servlet API
The javax.servlet and javax.servlet.http packages represent interfaces and classes
for servlet api.
The javax.servlet package contains many interfaces and classes that are used by
the servlet or web container. These are not specific to any protocol.
The javax.servlet.http package contains interfaces and classes that are
responsible for http requests only.
Let's see what are the interfaces of javax.servlet package.
Interfaces in javax.servlet package
There are many interfaces in javax.servlet package. They are as follows:
1. Servlet 2. ServletConfig
3. ServletRequest 4. ServletContext
5. ServletResponse 6. SingleThreadModel
7. RequestDispatcher 8. Filter

Classes in javax.servlet package

 There are many classes in javax.servlet package. They are as follows:
1. GenericServlet 2. ServletContextEvent
3. ServletInputStream 4. ServletRequestAttributeEvent
5. ServletOutputStream 6. ServletContextAttributeEvent
7. ServletRequestWrapper 8. ServletException
9. ServletResponseWrapper UnavailableException
10. ServletRequestEvent

Interfaces in javax.servlet.http package

There are many interfaces in javax.servlet.http package. They are as follows:
1. HttpServletRequest 2. HttpSessionAttributeListener
3. HttpServletResponse 4. HttpSessionBindingListener
5. HttpSession 6. HttpSessionActivationListener
7. HttpSessionListener

Classes in javax.servlet.http package

There are many classes in javax.servlet.http package. They are as follows:
1. HttpServlet 4. HttpServletResponseWrapper
2. Cookie 5. HttpSessionEvent
3. HttpServletRequestWrapper 6. HttpSessionBindingEvent

d. Explain the life cycle of a servlet application.

The web container maintains the life cycle of a servlet instance. Let's see the life
cycle of the servlet:
1. Servlet class is loaded.
2. Servlet instance is created.
3. init method is invoked.
4. service method is invoked.
5. destroy method is invoked.

As displayed in the above diagram, there are three states of a servlet: new, ready
and end. The servlet is in new state if servlet instance is created. After invoking
the init() method, Servlet comes in the ready state. In the ready state, servlet
 performs all the tasks. When the web container invokes the destroy() method, it
shifts to the end state.

e. Explain the architecture of JDBC.

JDBC Architecture
The JDBC API supports both two-tier and three-tier processing models for
database access but in general, JDBC Architecture consists of two layers −
• JDBC API: This provides the application-to-JDBC Manager connection.
• JDBC Driver API: This supports the JDBC Manager-to-Driver
Connection.
The JDBC API uses a driver manager and database-specific drivers to provide
transparent connectivity to heterogeneous databases.
The JDBC driver manager ensures that the correct driver is used to access each
data source. The driver manager is capable of supporting multiple concurrent
drivers connected to multiple heterogeneous databases.
Following is the architectural diagram, which shows the location of the driver
manager with respect to the JDBC drivers and the Java application −

f. Enlist and explain the steps of Database connectivity using JDBC API.
Fundamental Steps in JDBC
The fundamental steps involved in the process of connecting to a database and
executing a query consist of the following:
• Import JDBC packages.
• Load and register the JDBC driver.
• Open a connection to the database.
• Create a statement object to perform a query.
• Execute the statement object and return a query resultset.
• Process the resultset.
• Close the resultset and statement objects.
• Close the connection.
Q2. Attempt any three of the following: 15

a. Explain the importance of RequestDispatcher Interface in javax.servlet. Add

suitable example to explain the methods of the interface.
The RequestDispatcher interface provides the facility of dispatching the request
to another resource it may be html, servlet or jsp. This interface can also be used
to include the content of another resource also. It is one of the way of servlet
collaboration.
There are two methods defined in the RequestDispatcher interface.
Methods of RequestDispatcher interface
The RequestDispatcher interface provides two methods. They are:
1. public void forward(ServletRequest request,ServletResponse
response)throws ServletException,java.io.IOException:Forwards a
request from a servlet to another resource (servlet, JSP file, or HTML
file) on the server.

2. public void include(ServletRequest request,ServletResponse

response)throws ServletException,java.io.IOException:Includes the
content of a resource (servlet, JSP page, or HTML file) in the response.
index.html
<form action="servlet1" method="post">
Name:<input type="text" name="userName"/><br/>
Password:<input type="password" name="userPass"/><br/>
<input type="submit" value="login"/>
</form>
Login.java
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;
public class Login extends HttpServlet {

public void doPost(HttpServletRequest request, HttpServletResponse response)

throws ServletException, IOException {

response.setContentType("text/html");
PrintWriter out = response.getWriter();

String n=request.getParameter("userName");
String p=request.getParameter("userPass");

if(p.equals("servlet"){
RequestDispatcher rd=request.getRequestDispatcher("servlet2");
rd.forward(request, response);
}
else{
out.print("Sorry UserName or Password Error!");
RequestDispatcher rd=request.getRequestDispatcher("/index.html");
rd.include(request, response);

}
}

WelcomeServlet.java
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;

public class WelcomeServlet extends HttpServlet {

public void doPost(HttpServletRequest request, HttpServletResponse response

)
throws ServletException, IOException {

response.setContentType("text/html");
PrintWriter out = response.getWriter();

String n=request.getParameter("userName");
out.print("Welcome "+n);
}

web.xml
<web-app>
<servlet>
<servlet-name>Login</servlet-name>
 <servlet-class>Login</servlet-class>
</servlet>
<servlet>
<servlet-name>WelcomeServlet</servlet-name>
<servlet-class>WelcomeServlet</servlet-class>
</servlet>

<servlet-mapping>
<servlet-name>Login</servlet-name>
<url-pattern>/servlet1</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>WelcomeServlet</servlet-name>
<url-pattern>/servlet2</url-pattern>
</servlet-mapping>

<welcome-file-list>
<welcome-file>index.html</welcome-file>
</welcome-file-list>
</web-app>
b. Explain how java handles session management of a servlet application through
HTTPSession.
HttpSession interface
In such case, container creates a session id for each user.The container uses this
id to identify the particular user.An object of HttpSession can be used to perform
two tasks:
1. bind objects
2. view and manipulate information about a session, such as the session
identifier, creation time, and last accessed time.

index.html
<form action="servlet1">
Name:<input type="text" name="userName"/><br/>
<input type="submit" value="go"/>
</form>
FirstServlet.java
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;

public class FirstServlet extends HttpServlet {

public void doGet(HttpServletRequest request, HttpServletResponse response){

try{

response.setContentType("text/html");
PrintWriter out = response.getWriter();

String n=request.getParameter("userName");
out.print("Welcome "+n);

HttpSession session=request.getSession();
session.setAttribute("uname",n);

out.print("<a href='servlet2'>visit</a>");

out.close();

}catch(Exception e){System.out.println(e);}
}

}
SecondServlet.java
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;

public class SecondServlet extends HttpServlet {

public void doGet(HttpServletRequest request, HttpServletResponse response)

try{

response.setContentType("text/html");
PrintWriter out = response.getWriter();

HttpSession session=request.getSession(false);
String n=(String)session.getAttribute("uname");
out.print("Hello "+n);

out.close();

}catch(Exception e){System.out.println(e);}
}

}
<web-app>
 <servlet>
<servlet-name>s1</servlet-name>
<servlet-class>FirstServlet</servlet-class>
</servlet>

<servlet-mapping>
<servlet-name>s1</servlet-name>
<url-pattern>/servlet1</url-pattern>
</servlet-mapping>

<servlet>
<servlet-name>s2</servlet-name>
<servlet-class>SecondServlet</servlet-class>
</servlet>

<servlet-mapping>
<servlet-name>s2</servlet-name>
<url-pattern>/servlet2</url-pattern>
</servlet-mapping>
</web-app>

c. What is cookie? Explain the need of the creation of the same. Explain the methods
of cookie class that facilitative the creation, manipulation and deletion of the
cookies.
Cookies in Servlet
A cookie is a small piece of information that is persisted between the multiple
client requests.

A cookie has a name, a single value, and optional attributes such as a comment,
path and domain qualifiers, a maximum age, and a version number.

Useful Methods of Cookie class

There are given some commonly used methods of the Cookie class.
Method Description

public void setMaxAge(int Sets the maximum age of the cookie in

expiry) seconds.

public String getName() Returns the name of the cookie. The name
cannot be changed after creation.

public String getValue() Returns the value of the cookie.

public void changes the name of the cookie.

setName(String name)
 public void changes the value of the cookie.
setValue(String value)

1. public void addCookie(Cookie ck):method of HttpServletResponse

interface is used to add cookie in response object.
2. public Cookie[] getCookies():method of HttpServletRequest interface
is used to return all the cookies from the browser.
Delete Cookies with Servlet
To delete cookies is very simple. If you want to delete a cookie then you simply
need to follow up following three steps −
• Read an already existing cookie and store it in Cookie object.
• Set cookie age as zero using setMaxAge() method to delete an existing
cookie
• Add this cookie back into response header.

d. What is Non-Blocking I/O? Explain WriteListener and ReadListener performing

in Non-Blocking I/O?
Nonblocking I/O Support in javax.servlet.ServletInputStream
Method Description
Associates this input stream with a listener
object that contains callback methods to read
void setReadListener(ReadListener data asynchronously. You provide the listene
rl) object as an anonymous class or use another
mechanism to pass the input stream to the
read listener object.
Returns true if data can be read without
boolean isReady()
blocking.
boolean isFinished() Returns true when all the data has been read.

Table 18-5 Nonblocking I/O Support in javax.servlet.ServletOutputStream

Method Description
Associates this output stream with a
listener object that contains callback
void setWriteListener(WriteListener methods to write data asynchronously.
You provide the write listener object as an
wl) anonymous class or use another
mechanism to pass the output stream to the
write listener object.
Returns true if data can be written without
boolean isReady()
blocking.
Listener Interfaces for Nonblocking I/O Support
Interface Methods Description
void onDataAvailable() A ServletInputStream instance
ReadListener void onAllDataRead() calls these methods on its listener
void onError(Throwable t) when there is data available to
 read, when all the data has been
read, or when there is an error.
A ServletOutputStream instance
void onWritePossible() calls these methods on its listener
WriteListener when it is possible to write data
void onError(Throwable t)
without blocking or when there is
an error.

e. Explain the working of Non-Blocking I/O.

Non blocking I/O
It is Buffer-oriented
Channels are available for Non-blocking I/O operation
Selectors are available for Non-blocking I/O operation
Non blocking IO does not wait for the data to be read or write before returning.
Java NIO non- blocking mode allows the thread to request writing data to a
channel, but not wait for it to be fully written. The thread is allowed to go on and
do something else in a mean time.
java NIO is buffer oriented I/O approach. Data is read into a buffer from which it
is further processed using a channel. In NIO we deal with the channel and buffer
for I/O operation.
The major difference between a channel and a stream is:
o A stream can be used for one-way data transfer.
o A channel provides a two-way data transfer facility.
Therefore with the introduction of channel in java NIO, the non-blocking I/O
operation can be performed.
Let's see the interaction between channel, buffers, java program, data source and
data sink:

Channels
In Java NIO, the channel is a medium that transports the data efficiently between
the entity and byte buffers. It reads the data from an entity and places it inside
buffer blocks for consumption.
Channels act as gateway provided by java NIO to access the I/O mechanism.
Usually channels have one-to-one relationship with operating system file
descriptor for providing the platform independence operational feature.
 f. Explain about the file uploading feature of a servlet.
A Servlet can be used with an HTML form tag to allow users to upload files to
the server. An uploaded file could be a text file or image file or any document.
Creating a File Upload Form
The following HTM code below creates an uploader form. Following are the
important points to be noted down −
• The form method attribute should be set to POSTmethod and GET
method can not be used
• The form enctype attribute should be set to multipart/form-data.
• The form action attribute should be set to a servlet file which would handle
file uploading at backend server. Following example is using
UploadServlet servlet to upload file.
• To upload a single file you should use a single <input .../> tag with attribute
type="file". To allow multiple files uploading, include more than one
input tags with different values for the name attribute. The browser
associates a Browse button with each of them.

Q3. Attempt any three of the following: 15

a. What are directives in JSP? Explain page directive in detail. (With all its attributes)
These directives provide directions and instructions to the container, telling it how
to handle certain aspects of the JSP processing.
A JSP directive affects the overall structure of the servlet class. It usually has the
following form −
<%@ directive attribute = "value" %>
Directives can have a number of attributes which you can list down as key-value
pairs and separated by commas.
The blanks between the @ symbol and the directive name, and between the last
attribute and the closing %>, are optional.
There are three types of directive tag −
S.No. Directive & Description

<%@ page ... %>

1 Defines page-dependent attributes, such as scripting language,
error page, and buffering requirements.

<%@ include ... %>

2
Includes a file during the translation phase.

<%@ taglib ... %>

3
Declares a tag library, containing custom actions, used in the page
The page directive is used to provide instructions to the container. These
instructions pertain to the current JSP page. You may code page directives
anywhere in your JSP page. By convention, page directives are coded at the top
of the JSP page.
Following is the basic syntax of the page directive −
<%@ page attribute = "value" %>
Attributes
Following table lists out the attributes associated with the page directive −
S.N o. Attribute & Purpose

buffer
1 Specifies a buffering model for the output stream.
autoFlush
2 Controls the behavior of the servlet output buffer.
contentType
3 Defines the character encoding scheme.

errorPage
Defines the URL of another JSP that reports on Java unchecked
4
runtime exceptions.

isErrorPage
Indicates if this JSP page is a URL specified by another JSP page's
5
errorPage attribute.

extends
6 Specifies a superclass that the generated servlet must extend.

import
Specifies a list of packages or classes for use in the JSP as the Java
7
import statement does for Java classes.

info
Defines a string that can be accessed with the
8
servlet's getServletInfo() method.

isThreadSafe
9 Defines the threading model for the generated servlet.
language
10 Defines the programming language used in the JSP page.

session
Specifies whether or not the JSP page participates in HTTP
11
sessions

isELIgnored
Specifies whether or not the EL expression within the JSP page
12
will be ignored.
b. What is EL? Explain immediate EL, deferred EL, LValue and RValue in detail.
Expression Language (EL) is mechanism that simplifies the accessibility of the
data stored in Java bean component and other object like request, session and
application, etc.
Immediate Evaluation
All expressions using the ${} syntax are evaluated immediately. These
expressions can only be used within template text or as the value of a JSP tag
attribute that can accept runtime expressions.
The following example shows a tag whose value attribute references an
immediate evaluation expression that gets the total price from the session-scoped
bean named cart:
<fmt:formatNumber value="${sessionScope.cart.total}"/>
The JSP engine evaluates the expression, ${sessionScope.cart.total}, converts it,
and passes the returned value to the tag handler.
Immediate evaluation expressions are always read-only value expressions. The
expression shown above can only get the total price from the cart bean; it cannot
set the total price.
Deferred Evaluation
Deferred evaluation expressions take the form #{expr} and can be evaluated at
other phases of a page life cycle as defined by whatever technology is using the
expression. In the case of JavaServer Faces technology, its controller can
evaluate the expression at different phases of the life cycle depending on how the
expression is being used in the page.
The following example shows a JavaServer Faces inputText tag, which
represents a text field component into which a user enters a value.
The inputText tag’s value attribute references a deferred evaluation expression
that points to the name property of the customerbean.
<h:inputText id="name" value="#{customer.name}" />
For an initial request of the page containing this tag, the JavaServer Faces
implementation evaluates the #{customer.name} expression during the render
response phase of the life cycle. During this phase, the expression merely
accesses the value of name from the customerbean, as is done in immediate
evaluation.

c. Explain the advantages of JSTL over JSP.

Advantages of JSTL over JSP
1. Standard Tag: It provides a rich layer of the portable functionality of
JSP pages. It's easy for a developer to understand the code.
2. Code Neat and Clean: As scriplets confuse developer, the usage of JSTL
makes the code neat and clean.
3. Automatic JavabeansInterospection Support: It has an advantage of
JSTL over JSP scriptlets. JSTL Expression language handles JavaBean
code very easily. We don't need to downcast the objects, which has been
retrieved as scoped attributes. Using JSP scriptlets code will be
complicated, and JSTL has simplified that purpose.
 4. Easier for humans to read: JSTL is based on XML, which is very
similar to HTML. Hence, it is easy for the developers to understand.
5. Easier for computers to understand: Tools such as Dreamweaver and
front page are generating more and more HTML code. HTML tools do a
great job of formatting HTML code. The HTML code is mixed with the
scriplet code. As JSTL is expressed as XML compliant tags, it is easy for
HTML generation to parse the JSTL code within the document.

d. Explain JSTL core Tag Library.

The JSTL core tag provide variable support, URL management, flow control, etc.
The URL for the core tag is http://java.sun.com/jsp/jstl/core. The prefix of core
tag is c.
The core group of tags are the most commonly used JSTL tags. Following is the
syntax to include the JSTL Core library in your JSP −
<%@ taglib prefix = "c" uri = "http://java.sun.com/jsp/jstl/core" %>
Following table lists out the core JSTL Tags −
S.N o. Tag & Description
<c:out>
1 Like <%= ... >, but for expressions.
<c:set >
2 Sets the result of an expression evaluation in a 'scope'
<c:remove >
3 Removes a scoped variable (from a particular scope, if specified).

<c:catch>
Catches any Throwable that occurs in its body and optionally
4
exposes it.

<c:if>
Simple conditional tag which evalutes its body if the supplied
5
condition is true.

<c:choose>
Simple conditional tag that establishes a context for mutually
6 exclusive conditional operations, marked
by <when> and <otherwise>.

<c:when>
Subtag of <choose> that includes its body if its condition evalutes
7
to 'true'.

<c:otherwise >
Subtag of <choose> that follows the <when> tags and runs only
8
if all of the prior conditions evaluated to 'false'.
 <c:import>
9 Retrieves an absolute or relative URL and exposes its contents to
either the page, a String in 'var', or a Reader in 'varReader'.

<c:forEach >
10 The basic iteration tag, accepting many different collection types
and supporting subsetting and other functionality .

e. Explain the implicit objects of JSP.

There are 9 jsp implicit objects. These objects are created by the web
container that are available to all the jsp pages.
A list of the 9 implicit objects is given below:

1. request implicit object

The JSP implicit request object is an instance of a java class that

implements the javax.servlet.http.HttpServletRequest interface. It
represents the request made by the client. The request implicit object is
generally used to get request parameters, request attributes, header
information and query string values.

Example of JSP request implicit object

index.html

1. <form action="welcome.jsp">
2. <input type="text" name="uname">
3. <input type="submit" value="go"><br/>
4. </form>

welcome.jsp

1. <%
2. String name=request.getParameter("uname");
3. out.print("welcome "+name);
4. %>

2. response implicit object

The JSP implicit response object is an instance of a java class that

implements the javax.servlet.http.HttpServletResponse interface. It
represents the response to be given to the client. The response implicit
object is generally used to set the response content type, add cookie and
redirect the response.

Example of response implicit object

index.html

1. <form action="welcome.jsp">
2. <input type="text" name="uname">
 3. <input type="submit" value="go"><br/>
4. </form>

welcome.jsp

1. <%
2. response.sendRedirect("http://www.google.com");
3. %>

3. out implicit object

The JSP implicit out object is an instance of the javax.servlet.jsp.JspWriter

class. It represents the output content to be sent to the client. The out
implicit object is used to write the output content.

Example of out implicit object

In this example we are simply displaying date and time.

index.jsp

1. <html>
2. <body>
3. <% out.print("Today is:"+java.util.Calendar.getInstance().getTime()); %>
4. </body>
5. </html>

4. session implicit object

The JSP implicit session object is an instance of a java class that

implements the javax.servlet.http.HttpSession interface. It represents a
client specific conversation. The session implicit object is used to store
session state for a single user.

Example of session implicit object

index.html

1. <html>
2. <body>
3. <form action="welcome.jsp">
4. Enter User Name: <input type="text" name="uname">
5. <input type="submit" value="go"><br/>
6. </form>
7. </body>
8. </html>

welcome.jsp

1. <html>
2. <body>
 3. <%
4.
5. String name=request.getParameter("uname");
6. out.print("Welcome "+name);
7.
8. session.setAttribute("user",name);
9.
10. <a href="second.jsp">second jsp page</a>
11.
12. %>
13. </body>
14. </html>

second.jsp

1. <html>
2. <body>
3. <%
4.
5. String name=(String)session.getAttribute("user");
6. out.print("Hello "+name);
7.
8. %>
9. </body>
10. </html>

5. application implicit object

The JSP implicit application object is an instance of a java class that

implements the javax.servlet.ServletContext interface. It gives facility for a
JSP page to obtain and set information about the web application in which
it is running.

6. exception implicit object

The JSP implicit exception object is an instance of the java.lang.Throwable

class. It is available in JSP error pages only. It represents the occured
exception that caused the control to pass to the JSP error page.

Example of exception handling in jsp by the elements of page

directive

index.jsp

1. <form action="process.jsp">
2. No1:<input type="text" name="n1" /><br><br>
3. No2:<input type="text" name="n2" /><br><br>
4. <input type="submit" value="divide"/>
5. </form>

process.jsp

1. <%@ page errorPage="error.jsp" %>

2. <%
 3. int a=Integer.parseInt(request.getParameter(“n1”));
4. int b=Integer.parseInt(request.getParameter(“n2”));
5. int c=a/b;
6. out.print("division of numbers is: "+c);
7. %>

error.jsp

1. <%@ page isErrorPage="true" %>

2. <h3>An exception occured!</h3>
3. Exception is: <%= exception %>

7. config implicit object

The JSP implicit config object is an instance of the java class that
implements javax.servlet.ServletConfig interface. It gives facility for a JSP
page to obtain the initialization parameters available.

8. page implicit object

The JSP implicit page object is an instance of the java.lang.Object class. It

represents the current JSP page. That is, it serves as a reference to the java
servlet object that implements the JSP page on which it is accessed. It is not
advisable to use this page implict object often as it consumes large
memory.

9. pageContext implicit object

The JSP implicit pageContext object is an instance of the

javax.servlet.jsp.PageContext abstract class. It provides useful context
information. That is it provides methods to get and set attributes in different
scopes and for transfering requests to other resources. Also it contains the
reference to to implicit objects.

Example of pageContext implicit object

index.html

1. <html>
2. <body>
3. <form action="welcome.jsp">
4. <input type="text" name="uname">
5. <input type="submit" value="go"><br/>
6. </form>
7. </body>
8. </html>

welcome.jsp

1. <html>
2. <body>
3. <%
4.
5. String name=request.getParameter("uname");
 6. out.print("Welcome "+name);
7.
8. pageContext.setAttribute("user",name,PageContext.SESSION_SCOPE);
9.
10. <a href="second.jsp">second jsp page</a>
11.
12. %>
13. </body>
14. </html>

second.jsp

1. <html>
2. <body>
3. <%
4.
5. String name=(String)pageContext.getAttribute("user",PageContext.SESSI
ON_SCOPE);
6. out.print("Hello "+name);
7.
8. %>
9. </body>
10. </html>

f. Explain the various scope of JSP application.

The availability of a JSP object for use from a particular place of the application
is defined as the scope of that JSP object. Every object created in a JSP page will
have a scope. Object scope in JSP is segregated into four parts and they are page,
request, session and application.
• page
‘page’ scope means, the JSP object can be accessed only from within the
same page where it was created. The default scope for JSP objects created
 using <jsp:useBean> tag is page. JSP implicit objects out, exception,
response, pageContext, config and page have ‘page’ scope.
• request
A JSP object created using the ‘request’ scope can be accessed from any
pages that serves that request. More than one page can serve a single
request. The JSP object will be bound to the request object. Implicit
object request has the ‘request’ scope.
• session
‘session’ scope means, the JSP object is accessible from pages that belong
to the same session from where it was created. The JSP object that is
created using the session scope is bound to the session object. Implicit
object session has the ‘session’ scope.
• application
A JSP object created using the ‘application’ scope can be accessed from
any pages across the application. The JSP object is bound to the
application object. Implicit object application has the ‘application’ scope.

Q4. Attempt any three of the following: 15

a. Explain about enterprise bean container.

An Enterprise JavaBeans (EJB) container provides a run-time environment for
enterprise beans within the application server. The container handles all aspects
of an enterprise bean's operation within the application server and acts as an
intermediary between the user-written business logic within the bean and the rest
of the application server environment.
One or more EJB modules, each containing one or more enterprise beans, can be
installed in a single container.
The EJB container provides many services to the enterprise bean, including the
following:
Beginning, committing, and rolling back transactions as necessary.
Maintaining pools of enterprise bean instances ready for incoming requests and
moving these instances between the inactive pools and an active state, ensuring
that threading conditions within the bean are satisfied.
Most importantly, automatically synchronizing data in an entity bean's instance
variables with corresponding data items stored in persistent storage.

By dynamically maintaining a set of active bean instances and synchronizing bean

state with persistent storage when beans are moved into and out of active state, the
container makes it possible for an application to manage many more bean instances
than could otherwise simultaneously be held in the application server's memory.
In this respect, an EJB container provides services similar to virtual memory within
an operating system.
b. What are the different types of beans? Explain.
Types
EJB is primarily divided into three categories; following table lists their names
with brief descriptions −
 S.No Type & Description

1 Session Bean
Session bean stores data of a particular user for a single session. It
can be stateful or stateless. It is less resource intensive as
compared to entity bean. Session bean gets destroyed as soon as
user session terminates.

2 Entity Bean
Entity beans represent persistent data storage. User data can be
saved to database via entity beans and later on can be retrieved
from the database in the entity bean.

3 Message Driven Bean

Message driven beans are used in context of JMS (Java Messaging
Service). Message Driven Beans can consumes JMS messages
from external entities and act accordingly.

c. Explain the working behind message driven bean.

A message driven bean (MDB) is a bean that contains business logic. But, it is
invoked by passing the message. So, it is like JMS Receiver.
MDB asynchronously receives the message and processes it.
A message driven bean receives message from queue.
JMS (Java Message Service) is an API that provides the facility to create, send
and read messages. It provides loosely coupled, reliable and asynchronous
communication.
JMS is also known as a messaging service.

Understanding Messaging
Messaging is a technique to communicate applications or software components.
JMS is mainly used to send and receive message from one application to another.

Requirement of JMS
Generally, user sends message to application. But, if we want to send message
from one application to another, we need to use JMS API.

A message driven bean is like stateless session bean that encapsulates the
business logic and doesn't maintain state.

d. Explain the concept of naming service. Add suitable illustration to it.

 JNDI stands for Java Naming and Directory Interface. It is a set of API and service
interfaces. Java based applications use JNDI for naming and directory services.
In context of EJB, there are two terms.
• Binding − This refers to assigning a name to an EJB object, which can be
used later.
• Lookup − This refers to looking up and getting an object of EJB.
The JNDI architecture consists of an API and a service provider interface (SPI).
Java applications use the JNDI API to access a variety of naming and directory
services. The SPI enables a variety of naming and directory services to be
plugged in transparently, thereby allowing the Java application using the JNDI
API to access their services. See the following figure:

Any suitable example (practicals program snippet code will do)

e. Explain basic look up in JNDI. Also explain resource injection in JNDI.
JNDI (Java Naming and Directory Interface) organizes its names into a
hierarchy. A name can be any string such as "com.mydomain.ejb.MyBean". A
name can also be an object that implements the Name interface; however a
string is the most common way to name an object. A name is bound to an object
in the directory by storing either the object or a reference to the object in the
directory service identified by the name.
The JNDI API defines a context that specifies where to look for an object. The
initial context is typically used as a starting point.
In the simplest case, an initial context must be created using the specific
implementation and extra parameters required by the implementation. The initial
context will be used to look up a name. The initial context is analogous to the
root or top of a directory tree for a file system. Below is an example of creating
an initial context:

Hashtable contextArgs = new Hashtable();

// First you must specify the context factory.

contextArgs.put( Context.INITIAL_CONTEXT_FACTORY,
"com.jndiprovider.TheirContextFactory" );
 // The next argument is the URL specifying where the data store is:
contextArgs.put( Context.PROVIDER_URL, "jndiprovider-database" );

// (You may also have to provide security credentials)

// Next you create the initial context

Context myCurrentContext = new InitialContext(contextArgs);

A context is then used to look up previously bound names in that context. For
example:

MyBean myBean = (MyBean)

myCurrentContext.lookup("com.mydomain.MyBean");

Alternative to above code is as below:

The Context object can also be configured by adding jndi.properties file in
classpath containing initial context factory class name and provider URL. The
above code will be reduced as shown below:

//just need to create initial context object, it will try to read jndi.properties file
from the classpath.
Context myCurrentContext = new InitialContext();

A context is then used to look up previously bound names in that context. For
example:

MyBean myBean = (MyBean)

myCurrentContext.lookup("com.mydomain.MyBean");

Resource injection
One of the simplification features of Java EE is the implementation of basic
Resource Injection to simplify web and EJB components.
Resource injection enables you to inject any resource available in the JNDI
namespace into any container-managed object, such as a servlet, an enterprise
bean, or a managed bean. For eg, we can use resource injection to inject data
sources, connectors, or any other desired resources available in the JNDI
namespace.
The type we’ll use for the reference to the instance happen to be injected is
usually an interface, which would decouple our code from the implementation of
the resource.
For better understanding of the above statement let’s take a look at the example.
The resource injection can be performed in the following three ways:
· Field Injection
· Method Injection
· Class injection
f. Explain the life cycle of an interceptor.

Interceptors are used in conjunction with Java EE managed classes to allow

developers to invoke interceptor methods on an associated target class, in
conjunction with method invocations or lifecycle events. Common uses of
interceptors are logging, auditing, and profiling.

An interceptor can be defined within a target class as an interceptor method, or in

an associated class called an interceptor class. Interceptor classes contain methods
that are invoked in conjunction with the methods or lifecycle events of the target
class.

Interceptor classes and methods are defined using metadata annotations, or in the
deployment descriptor of the application containing the interceptors and target
classes.

Interceptor Lifecycle

Interceptor classes have the same lifecycle as their associated target class. When a
target class instance is created, an interceptor class instance is also created for each
declared interceptor class in the target class. That is, if the target class declares
multiple interceptor classes, an instance of each class is created when the target
class instance is created. The target class instance and all interceptor class
instances are fully instantiated before any @PostConstruct callbacks are invoked,
and any @PreDestroy callbacks are invoked before the target class and interceptor
class instances are destroyed.
Q5. Attempt any three of the following: 15

a. Explain the persistent standards available in java.

Java Persistence API
The Java Persistence API (JPA) is a Java standards–based solution for
persistence. Persistence uses an object/relational mapping approach to bridge the
gap between an object-oriented model and a relational database. The Java
Persistence API can also be used in Java SE applications outside of the Java EE
environment. Java Persistence consists of the following areas:
• The Java Persistence API
• The query language
• Object/relational mapping metadata
The Java Persistence API (JPA) is a specification of Java. It is used to persist
data between Java object and relational database. JPA acts as a bridge between
object-oriented domain models and relational database systems.
As JPA is just a specification, it doesn't perform any operation by itself. It
requires an implementation. So, ORM tools like Hibernate, TopLink and iBatis
implements JPA specifications for data persistence.
JPA Versions
The first version of Java Persistenece API, JPA 1.0 was released in 2006 as a part
of EJB 3.0 specification.
Following are the other development versions released under JPA specification: -
o JPA 2.0 - This version was released in the last of 2009. Following are the
important features of this version: -
o It supports validation.
o It expands the functionality of object-relational mapping.
o It shares the object of cache support.
o JPA 2.1 - The JPA 2.1 was released in 2013 with the following features: -
o It allows fetching of objects.
o It provides support for criteria update/delete.
o It generates schema.
o JPA 2.2 - The JPA 2.2 was released as a development of maintainenece in
2017. Some of its important feature are: -
o It supports Java 8 Date and Time.
o It provides @Repeatable annotation that can be used when we
want to apply the same annotations to a declaration or type use.
o It allows JPA annotation to be used in meta-annotations.
o It provides an ability to stream a query result.

b. Draw and explain the architecture of hibernate framework.

The Hibernate architecture is categorized in four layers.
o Java application layer
o Hibernate framework layer
o Backhand api layer
o Database layer
Let's see the diagram of hibernate architecture:
This is the high level architecture of Hibernate with mapping file and
configuration file.

Elements of Hibernate Architecture

For creating the first hibernate application, we must know the elements of Hibe
SessionFactory
The SessionFactory is a factory of session and client of ConnectionProvider. It
holds second level cache (optional) of data. The org.hibernate.SessionFactory
interface provides factory method to get the object of Session.
Session
The session object provides an interface between the application and data stored
in the database. It is a short-lived object and wraps the JDBC connection. It is
factory of Transaction, Query and Criteria. It holds a first-level cache
(mandatory) of data. The org.hibernate.Session interface provides methods to
insert, update and delete the object. It also provides factory methods for
Transaction, Query and Criteria.
 Transaction
The transaction object specifies the atomic unit of work. It is optional. The
org.hibernate.Transaction interface provides methods for transaction
management.
ConnectionProvider
It is a factory of JDBC connections. It abstracts the application from
DriverManager or DataSource. It is optional.
TransactionFactory
It is a factory of Transaction. It is optional.

c. Explain JPA Architecture with the help of a neat diagram.

Class Level Architecture
The following image shows the class level architecture of JPA. It shows the core
classes and interfaces of JPA.

The following table describes each of the units shown in the above architecture.
Units Description

EntityManagerFactory This is a factory class of EntityManager. It

creates and manages multiple EntityManager
instances.

EntityManager It is an Interface, it manages the persistence

operations on objects. It works like factory
for Query instance.

Entity Entities are the persistence objects, stores as

records in the database.
 EntityTransaction It has one-to-one relationship with
EntityManager. For each EntityManager,
operations are maintained by
EntityTransaction class.

Persistence This class contain static methods to obtain

EntityManagerFactory instance.

Query This interface is implemented by each JPA

vendor to obtain relational objects that meet
the criteria.

d. What is Impedance Mismatch? How it can be solved?

First problem, what if we need to modify the design of our database after having
developed a few pages or our application? Second, loading and storing objects in
a relational database exposes us to the following five mismatch problems −
Sr.No. Mismatch & Description

1 Granularity
Sometimes you will have an object model, which has more
classes than the number of corresponding tables in the database.

2 Inheritance
RDBMSs do not define anything similar to Inheritance, which is
a natural paradigm in object-oriented programming languages.

3 Identity
An RDBMS defines exactly one notion of 'sameness': the
primary key. Java, however, defines both object identity (a==b)
and object equality (a.equals(b)).

4 Associations
Object-oriented languages represent associations using object
references whereas an RDBMS represents an association as a
foreign key column.

5 Navigation
The ways you access objects in Java and in RDBMS are
fundamentally different.
The Object-Relational Mapping (ORM) is the solution to handle all the above
impedance mismatches
ORM stands for Object-Relational Mapping (ORM) is a programming technique
for converting data between relational databases and object oriented programming
languages such as Java, C#, etc.
An ORM system has the following advantages over plain JDBC −
Sr.No. Advantages
 1 Let’s business code access objects rather than DB tables.

2 Hides details of SQL queries from OO logic.

3 Based on JDBC 'under the hood.'

4 No need to deal with the database implementation.

5 Entities based on business concepts rather than database structure.

6 Transaction management and automatic key generation.

7 Fast development of application.

e. Explain different components of hibernate.

Core components of Hibernate
Below are the important elements of Hibernate
• hibernate.cfg.xml: This file has database connection details
• hbm.xml or Annotation: Defines the database table mapping with
POJO. Also defines the relation between tables in java way.
• SessionFactory:
o There will be a session factory per database.
o The SessionFacory is built once at start-up
o It is a thread safe class
o SessionFactory will create a new Session object when requested
Session:
o The Session object will get physical connection to the database.
o Session is the Java object used for any DB operations.
o Session is not thread safe. Hence do not share hibernate session
between threads
o Session represents unit of work with database
o Session should be closed once the task is completed

f. Explain the modus operandi behind hibernate application.