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 multi-tiered, web-based applications.

A J2EE module consists of one or more J2EE components for the same container type and one component deployment descriptor of that type.  

1.Application client module
2. Web module
3. Enterprise JavaBeans module
4. Resource adapter module

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.

A container that includes support for the applet programming model.

A first-tier J2EE client component that executes in its own Java virtual machine. Application clients have access
to some J2EE platform APIs.

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)

A software unit that consists of one or more classes and an application client deployment descriptor.

An XML file used to configure resources for a JavaServer Faces application, to define navigation rules for
the application, and to register converters, validators, listeners, renderers, and components with the
application.

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.

An authorization rule that determines who is permitted to access a Web resource collection.

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.

The mechanism whereby data transfer between an entity bean's variables and a resource manager is
managed by the entity bean.

Generating the code needed to process a well-defined portion of XML data.

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.

A method of an enterprise bean that implements the business logic or rules of an application.

Same as caller principal.

A deletion that triggers another deletion. A cascade delete can be specified for an entity bean that has
container-managed persistence.

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.

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.

A trusted organization that issues public key certificates and provides identification to the bearer.

The principal that identifies the invoker of the enterprise bean method.

Component methods called by the container to notify the component of important events in its life cycle.

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.

Wiring UI components to back-end data sources such as backing bean properties.

A transaction whose boundaries are defined by an enterprise bean.

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.

B2B stands for Business-to-business.

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.

A qualifier on an XML tag that provides additional information.

The process of saving the state of an object and restoring it

A vendor that provides the Java classes that implement components' methods, JSP page definitions, and
any required deployment descriptors.

A container that supports application client components

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.

JOBSMATE.COM

A person who combines J2EE components and modules into deployable application units.

The application client module contains:

--class files,
--an application client deployment descriptor.
Application client modules are packaged as JAR files with a .jar extension.

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.

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.

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.

A mechanism whereby security information needed for signing on to a resource is provided by an
application component.

The mechanism whereby data transfer between an entity bean's variables and a resource manager is
managed by the entity bean's container.

An architecture for integration of J2EE products with enterprise information systems. There are two parts
to this architecture: a resource adapter provided by an enterprise information system vendor and the J2EE
product that allows this resource adapter to plug in. This architecture defines a set of contracts that a
resource adapter must support to plug in to a J2EE product-for example, transactions, security, and
resource management.

A transaction whose boundaries are defined by an EJB container. An entity bean must use
container-managed transactions.

An object bound into the context associated with a servlet.

A method defined in the home interface and invoked by a client to create an enterprise bean

Cascading style sheet. A stylesheet used with HTML and XML documents to add a style to all elements
marked with a particular tag, for the direction of browsers or other presentation mechanisms.

The contents of an element in an XML stream, generally used when the element does not contain any
subelements. When it does, the term content is generally used. When the only text in an XML structure is
contained in simple elements and when elements that have subelements have little or no data mixed in,
then that structure is often thought of as XML data, as opposed to an XML document.

An XML file provided with each module and J2EE application that describes how they should be
deployed. The deployment descriptor directs a deployment tool to deploy a module or application with
specific container options and describes specific configuration requirements that a deployer must resolve.

In general, an XML structure in which one or more elements contains text intermixed with subelements..

An authentication mechanism in which a Web application authenticates itself to a Web server by sending
the server a message digest along with its HTTP request message. The digest is computed by employing a
one-way hash algorithm to a concatenation of the HTTP request message and the client's password. The
digest is typically much smaller than the HTTP request and doesn't contain the password.

The top-level directory of a WAR. The document root is where JSP pages, client-side classes and archives,
and static Web resources are stored.

In a JMS publish/subscribe messaging system, a subscription that continues to exist whether or not there is
a current active subscriber object. If there is no active subscriber, the JMS provider retains the
subscription's messages until they are received by the subscription or until they expire.

A JAR archive that contains an EJB module.

Electronic Business XML. A group of specifications designed to enable enterprises to conduct business
through the exchange of XML-based messages. It is sponsored by OASIS and the United Nations Centre
for the Facilitation of Procedures and Practices in Administration, Commerce and Transport
(U.N./CEFACT).

A vendor that supplies an EJB server.

A tag that does not enclose any content.

An entity that provides enterprise information system-specific functionality to its clients. Examples are a
record or set of records in a database system, a business object in an enterprise resource planning system,
and a transaction program in a transaction processing system.

Defines the queries for the finder and select methods of an entity bean having container-managed
persistence. A subset of SQL92, EJB QL has extensions that allow navigation over the relationships
defined in an entity bean's abstract schema.

A SAX parsing error is generally a validation error; in other words, it occurs when an XML document is
not valid, although it can also occur if the declaration specifies an XML version that the parser cannot
handle. See also fatal error, warning.

An entity that exists as an external XML file, which is included in the XML document using an entity
reference.

A fatal error occurs in the SAX parser when a document is not well formed or otherwise cannot be
processed. See also error, warning.

A concatenation of XSLT transformations in which the output of one transformation becomes the input of
the next.

An authentication mechanism in which a Web container provides an application-specific form for logging
in. This form of authentication uses Base64 encoding and can expose user names and passwords unless all
connections are over SSL.

An object that can be used to obtain a reference to the home interface. A home handle can be serialized and written to
stable storage and deserialized to obtain the reference.

The international standard for country codes maintained by the International Organization for Standardization (ISO).

One of two interfaces for an enterprise bean. The home interface defines zero or more methods for managing an
enterprise bean. The home interface of a session bean defines create and remove methods, whereas the home interface
of an entity bean defines create, finder, and remove methods.

An entity that is referenced as part of an XML document's content, as distinct from a parameter entity, which is
referenced in the DTD. A general entity can be a parsed entity or an unparsed entity.

A method defined in the home interface and invoked by a client to locate an entity bean.

That part of a DTD that is defined by references to external DTD files.

XML

A component architecture for the development and deployment of object-oriented, distributed, enterprise-level
applications. Applications written using the Enterprise JavaBeans architecture are scalable, transactional, and secure.

A J2EE component that implements a business task or business entity and is hosted by an EJB container; either an
entity bean, a session bean, or a message-driven bean.

A deployable unit that consists of one or more enterprise beans and an EJB deployment descriptor.

Enterprise Archive file. A JAR archive that contains a J2EE application.

An API for accessing and manipulating XML documents as tree structures. DOM provides platform-neutral,
language-neutral interfaces that enables programs and scripts to dynamically access and modify content and structure
in XML documents.

A person who installs J2EE modules and applications into an operational environment.

A JMS administered object that encapsulates the identity of a JMS queue or topic. See point-to-point messaging
system, publish/subscribe messaging system.

The process whereby software is installed into an operational environment.

Mechanisms used in an application that are expressed in a declarative syntax in a deployment descriptor.

Document-driven programming. The use of XML to define applications

Compatibility test suite. A suite of compatibility tests for verifying that a J2EE product complies with the J2EE
platform specification.

A name that gets mapped to the document root of a Web application.

In an XML document, the part that occurs after the prolog, including the root element and everything it contains.

The mechanism whereby security information needed for signing on to a resource is supplied by the container.

An entity that provides life-cycle management, security, deployment, and runtime services to J2EE components. Each
type of container (EJB, Web, JSP, servlet, applet, and application client) also provides component-specific services.

A parameter that initializes the context associated with a servlet.

Independent software vendor

A self-contained functional software unit supported by a container and configurable at
deployment time. The J2EE specification defines the following J2EE components: Application
clients and applets are components that run on the client. Java servlet and JavaServer Pages (JSP)
technology components are Web components that run on the server. Enterprise JavaBeans (EJB)
components (enterprise beans) are business components that run on the server. J2EE components
are written in the Java programming language and are compiled in the same way as any program
in the language. The difference between J2EE components and "standard" Java classes is that
J2EE components are assembled into a J2EE application, verified to be well formed and in
compliance with the J2EE specification, and deployed to production, where they are run and
managed by the J2EE server or client container.

An implementation that conforms to the J2EE platform specification.

The runtime portion of a J2EE product. A J2EE server provides EJB or Web containers or both.

Abbreviate of Java 2 Platform, Standard Edition

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 multitiered,
Web-based applications.

The core Java technology platform.

An API for accessing various kinds of XML registries.

An API that allows applications and J2EE servers to access transactions.

A Java class that can be manipulated by tools and composed into applications. A JavaBeans component must adhere
to certain property and event interface conventions.

An extensible Web technology that uses static data, JSP elements, and server-side Java objects to generate dynamic
content for a client. Typically the static data is HTML or XML elements, and in many cases the client is a Web
browser.

A client program that uses the JAXR API to access a business registry via a JAXR provider.

A Java language program that sends or receives messages.

Any deployable unit of J2EE functionality. This can be a single J2EE module or a group of modules packaged into an EAR file
along with a J2EE application deployment descriptor. J2EE applications are typically engineered to be distributed across multiple
computing tiers.

A software unit that consists of one or more J2EE components of the same container type and one deployment descriptor of that
type. There are four types of modules: EJB, Web, application client, and resource adapter. Modules can be deployed as stand-alone
units or can be assembled into a J2EE application.

A highly optimized Java runtime environment targeting a wide range of consumer products, including pagers, cellular phones,
screen phones, digital set-top boxes, and car navigation systems.

An API for processing XML documents. JAXP leverages the parser standards SAX and DOM so that you can choose to parse your
data as a stream of events or to build a tree-structured representation of it. JAXP supports the XSLT standard, giving you control
over the presentation of the data and enabling you to convert the data to other XML documents or to other formats, such as HTML.
JAXP provides namespace support, allowing you to work with schema that might otherwise have naming conflicts.

An API for building Web services and clients that use remote procedure calls and XML.

An API for invoking operations on enterprise messaging systems.

A set of packages that enable secure Internet communications.

Specifies the implementation of a transaction manager that supports JTA and implements the Java mapping of the Object
Management Group Object Transaction Service 1.1 specification at the level below the API.

An API for sending and receiving email.

A tag library that encapsulates core functionality common to many JSP applications. JSTL has support for common,
structural tasks such as iteration and conditionals, tags for manipulating XML documents, internationalization and
locale-specific formatting tags, SQL tags, and functions.

An implementation of the JAXR API that provides access to a specific registry provider or to a class of registry
providers that are based on a common specification.

A vendor that supplies a J2EE product.