Java Message Service API

<< Java Servlet Technology | Java API for XML Processing >>

Java Message Service API

The following features support the GUI components:

Input validation

Event handling

Data conversion between model objects and components

Managed model object creation

Page navigation configuration

All this functionality is available using standard Java APIs and XML-based configuration files.

Java Message Service API

The Java Message Service (JMS) API is a messaging standard that allows Java EE application
components to create, send, receive, and read messages. It enables distributed communication
that is loosely coupled, reliable, and asynchronous.

Java Transaction API

The Java Transaction API (JTA) provides a standard interface for demarcating transactions.
The Java EE architecture provides a default auto commit to handle transaction commits and
rollbacks. An auto commit means that any other applications that are viewing data will see the
updated data after each database read or write operation. However, if your application performs
two separate database access operations that depend on each other, you will want to use the JTA
API to demarcate where the entire transaction, including both operations, begins, rolls back,
and commits.

JavaMail API

Java EE applications use the JavaMail

API to send email notifications. The JavaMail API has

two parts: an application-level interface used by the application components to send mail, and a
service provider interface. The Java EE platform includes JavaMail with a service provider that
allows application components to send Internet mail.

JavaBeans Activation Framework

The JavaBeans Activation Framework (JAF) is included because JavaMail uses it. JAF provides
standard services to determine the type of an arbitrary piece of data, encapsulate access to it,
discover the operations available on it, and create the appropriate JavaBeans component to
perform those operations.

Java EE 5 APIs

Chapter 1 · Overview