Q.1 What is J2EE?
Ans: J2EE
is an environment for developing and deploying enterprise applications.
The J2EE platform consists of a set of services, application
programming interfaces (APIs), and protocols that provide the
functionality for developing multitier, web-based applications.
Q.2 What is the J2EE module?
Ans:
A J2EE module consists of one or more J2EE components for the same
container type and one component deployment descriptor of that type.
Q.3 What are the components of J2EE application?
Ans:
A J2EE component is a self-contained functional software unit that is
assembled into a J2EE application with its related classes and files and
communicates with other components. The J2EE specification defines the
following J2EE components:
Application clients and applets are client components.
Java Servlet and JavaServer PagesTM (JSPTM) technology components are web components.
Enterprise JavaBeansTM (EJBTM) components (enterprise beans) are business components.
Resource adapter components provided by EIS and tool vendors.
Java Servlet and JavaServer PagesTM (JSPTM) technology components are web components.
Enterprise JavaBeansTM (EJBTM) components (enterprise beans) are business components.
Resource adapter components provided by EIS and tool vendors.
Q.4 What are the four types of J2EE modules?
Ans: 1. Application client module
2. Web module
3. Enterprise JavaBeans module
4. Resource adapter module
2. Web module
3. Enterprise JavaBeans module
4. Resource adapter module
Q.5 What does application client module contain?
Ans: The application client module contains:
class files, an application client deployment descriptor.
Application client modules are packaged as JAR files with a .jar extension.
class files, an application client deployment descriptor.
Application client modules are packaged as JAR files with a .jar extension.
Q..6 What does web module contain?
Ans: The web module contains:
JSP files,
class files for servlets,
GIF and HTML files, and Web deployment descriptor.
Web modules are packaged as JAR files with a .war (Web ARchive) extension.
JSP files,
class files for servlets,
GIF and HTML files, and Web deployment descriptor.
Web modules are packaged as JAR files with a .war (Web ARchive) extension.
Q.7 What are the differences between Ear, Jar and War files? Under what circumstances should we use each one?
Ans:
There are no structural differences between the files; they are all
archived using zip-jar compression. However, they are intended for
different purposes.
–Jar files (files with a .jar extension) are intended to hold generic libraries of Java classes, resources, auxiliary files, etc.
–War files (files with a .war extension) are intended to contain complete Web applications. In this context, a Web application is defined as a single group of files, classes, resources, .jar files that can be packaged and accessed as one servlet context.
–Ear files (files with a .ear extension) are intended to contain complete enterprise applications. In this context, an enterprise application is defined as a collection of .jar files, resources, classes, and multiple Web applications.
Each type of file (.jar, .war, .ear) is processed uniquely by application servers, servlet containers, EJB containers, etc.
–Jar files (files with a .jar extension) are intended to hold generic libraries of Java classes, resources, auxiliary files, etc.
–War files (files with a .war extension) are intended to contain complete Web applications. In this context, a Web application is defined as a single group of files, classes, resources, .jar files that can be packaged and accessed as one servlet context.
–Ear files (files with a .ear extension) are intended to contain complete enterprise applications. In this context, an enterprise application is defined as a collection of .jar files, resources, classes, and multiple Web applications.
Each type of file (.jar, .war, .ear) is processed uniquely by application servers, servlet containers, EJB containers, etc.
Q.8 What is the difference between Session bean and Entity bean ?
Ans: The Session bean and Entity bean are two main parts of EJB container.
Session Bean
represents a workflow on behalf of a client
one-to-one logical mapping to a client.
created and destroyed by a client
not permanent objects
lives its EJB container(generally) does not survive system shut down
two types: stateless and stateful beans
Entity Bean
represents persistent data and behavior of this data
can be shared among multiple clients
persists across multiple invocations
findable permanent objects
outlives its EJB container, survives system shutdown
two types: container managed persistence(CMP) and bean managed persistence(BMP)
Session Bean
represents a workflow on behalf of a client
one-to-one logical mapping to a client.
created and destroyed by a client
not permanent objects
lives its EJB container(generally) does not survive system shut down
two types: stateless and stateful beans
Entity Bean
represents persistent data and behavior of this data
can be shared among multiple clients
persists across multiple invocations
findable permanent objects
outlives its EJB container, survives system shutdown
two types: container managed persistence(CMP) and bean managed persistence(BMP)
Q.9 What is “applet”?
Ans:
A J2EE component that typically executes in a Web browser but can
execute in a variety of other applications or devices that support the
applet programming model.
Q.0 What is “applet container”?
Ans: A container that includes support for the applet programming model.
Q.11 What is “application assembler”?
Ans: A person who combines J2EE components and modules into deployable application units.
Q.12 What is “application client”?
Ans: A
first-tier J2EE client component that executes in its own Java virtual
machine. Application clients have access to some J2EE platform APIs.
Q.13 What is “application client container”?
Ans: A container that supports application client components.
Q.14 What is “application client module”?
Ans: A software unit that consists of one or more classes and an application client deployment descriptor.
Q.15 What is “application component provider”?
Ans:
A vendor that provides the Java classes that implement components’
methods, JSP page definitions, and any required deployment descriptors.
Q.16 What is “application configuration resource file”?
Ans:
An XML file used to configure resources for a Java Server Faces
application, to define navigation rules for the application, and to
register converters, Validator, listeners, renders, and components with
the application.
Q.17 What is “archiving”?
Ans: The process of saving the state of an object and restoring it.
Q.18 What is “asant”?
Ans:
A Java-based build tool that can be extended using Java classes. The
configuration files are XML-based, calling out a target tree where
various tasks get executed..
Q.19 What is authentication?
Ans:
The process that verifies the identity of a user, device, or other
entity in a computer system, usually as a prerequisite to allowing
access to resources in a system. The Java servlet specification requires
three types of authentication-basic, form-based, and mutual-and
supports digest authentication.
0 comments:
Post a Comment