Question 1 :
What is J2EE?
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.
Question 2 :
What is the J2EE module?
A J2EE module consists of one or more J2EE components for the same container type and one component deployment descriptor of that type.
Question 3 :
What are the components of J2EE application?
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.
Question 4 :
What are the four types of J2EE modules?
1. Application client module
2. Web module
3. Enterprise JavaBeans module
4. Resource adapter module
Question 5 :
What does application client module contain?
The application client module contains:
an application client deployment descriptor.
Application client modules are packaged as JAR files with a .jar extension.
Question 6 :
What does web module contain?
The web module contains:
JSP files, class files for servlets, GIF and HTML files, and a Web deployment descriptor.
Web modules are packaged as JAR files with a .war (Web ARchive) extension.
Question 7 :
What are the differences between Ear, Jar and War files? Under what circumstances should we use each one?
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.
Question 8 :
What is the difference between Session bean and Entity bean ?
The Session bean and Entity bean are two main parts of EJB container.
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
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)
Question 9 :
What is "applet" ?
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.
Question 10 :
What is "applet container" ?
A container that includes support for the applet programming model.
Question 11 :
What is "application assembler" ?
A person who combines J2EE components and modules into deployable application units.
Question 12 :
What is "application client" ?
A first-tier J2EE client component that executes in its own Java virtual machine. Application clients have access to some J2EE platform APIs.
Question 13 :
What is "application client container" ?
A container that supports application client components.
Question 14 :
What is "application client module" ?
A software unit that consists of one or more classes and an application client deployment descriptor.
Question 15 :
What is "application component provider" ?
A vendor that provides the Java classes that implement components' methods, JSP page definitions, and any required deployment descriptors.
Question 16 :
What is "application configuration resource file" ?
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.
Question 17 :
What is "archiving" ?
The process of saving the state of an object and restoring it.
Question 18 :
What is "asant" ?
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.
Question 19 :
What is "attribute"?
A qualifier on an XML tag that provides additional information.
Question 20 :
What is authentication ?
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.
Question 21 :
What is authorization ?
The process by which access to a method or resource is determined. Authorization depends on the determination of whether the principal associated with a request through authentication is in a given security role. A security role is a logical grouping of users defined by the person who assembles the application. A deployer maps security roles to security identities. Security identities may be principals or groups in the operational environment.
Question 22 :
What is authorization constraint ?
An authorization rule that determines who is permitted to access a Web resource collection.
Question 23 :
What is B2B ?
B2B stands for Business-to-business.
Question 24 :
What is backing bean ?
A JavaBeans component that corresponds to a JSP page that includes JavaServer Faces components. The backing bean defines properties for the components on the page and methods that perform processing for the component. This processing includes event handling, validation, and processing associated with navigation.
Question 25 :
What is basic authentication ?
An authentication mechanism in which a Web server authenticates an entity via a user name and password obtained using the Web application's built-in authentication mechanism.
Question 26 :
What is bean-managed persistence ?
The mechanism whereby data transfer between an entity bean's variables and a resource manager is managed by the entity bean.
Question 27 :
What is bean-managed transaction ?
A transaction whose boundaries are defined by an enterprise bean.
Question 28 :
What is binding (XML) ?
Generating the code needed to process a well-defined portion of XML data.
Question 29 :
What is binding (JavaServer Faces technology) ?
Wiring UI components to back-end data sources such as backing bean properties.
Question 30 :
What is build file ?
The XML file that contains one or more asant targets. A target is a set of tasks you want to be executed. When starting asant, you can select which targets you want to have executed. When no target is given, the project's default target is executed.
Question 31 :
What is business logic ?
The code that implements the functionality of an application. In the Enterprise JavaBeans architecture, this logic is implemented by the methods of an enterprise bean.
Question 32 :
What is business method ?
A method of an enterprise bean that implements the business logic or rules of an application.
Question 33 :
What is callback methods ?
Component methods called by the container to notify the component of important events in its life cycle.
Question 34 :
What is caller ?
Same as caller principal.
Question 35 :
What is caller principal ?
The principal that identifies the invoker of the enterprise bean method.
Question 36 :
What is cascade delete ?
A deletion that triggers another deletion. A cascade delete can be specified for an entity bean that has container-managed persistence.
Question 37 :
What is CDATA ?
A predefined XML tag for character data that means "don't interpret these characters," as opposed to parsed character data (PCDATA), in which the normal rules of XML syntax apply. CDATA sections are typically used to show examples of XML syntax.
Question 38 :
What is certificate authority ?
A trusted organization that issues public key certificates and provides identification to the bearer.
Question 39 :
What is client-certificate authentication ?
An authentication mechanism that uses HTTP over SSL, in which the server and, optionally, the client authenticate each other with a public key certificate that conforms to a standard that is defined by X.509 Public Key Infrastructure.
Question 40 :
What is comment ?
In an XML document, text that is ignored unless the parser is specifically told to recognize it.
Question 41 :
What is commit ?
The point in a transaction when all updates to any resources involved in the transaction are made permanent.
Question 42 :
What is component contract ?
The contract between a J2EE component and its container. The contract includes life-cycle management of the component, a context interface that the instance uses to obtain various information and services from its container, and a list of services that every container must provide for its components.
Question 43 :
What is component-managed sign-on ?
A mechanism whereby security information needed for signing on to a resource is provided by an application component.
Question 44 :
What is connector ?
A standard extension mechanism for containers that provides connectivity to enterprise information systems. A connector is specific to an enterprise information system and consists of a resource adapter and application development tools for enterprise information system connectivity. The resource adapter is plugged in to a container through its support for system-level contracts defined in the Connector architecture.
Question 45 :
What is container-managed persistence ?
The mechanism whereby data transfer between an entity bean's variables and a resource manager is managed by the entity bean's container.
Question 46 :
What is container-managed sign-on ?
The mechanism whereby security information needed for signing on to a resource is supplied by the container.
Question 47 :
What is container-managed transaction ?
A transaction whose boundaries are defined by an EJB container. An entity bean must use container-managed transactions.
Question 48 :
What is content ?
In an XML document, the part that occurs after the prolog, including the root element and everything it contains.
Question 49 :
What is context attribute ?
An object bound into the context associated with a servlet.
Question 50 :
What is context root ?
A name that gets mapped to the document root of a Web application.