Java Database Connectivity 2.0; Java Servlet 2.3; Javaserver Pages 1.2; Java Message Service 1.0 - MACROMEDIA 38000382 - JRun - Mac Getting Started Manual

Java Database Connectivity 2.0

The Java Database Connectivity (JDBC) API is a standard Java extension for data access
that lets Java programmers code to a unified relational database API. By using JDBC, you
can issue SQL statements and process database results from Java programming language
methods. Clients program to the JDBC API, which is implemented by a JDBC Driver,
an adapter that can communicate with a particular database in a proprietary way.
The JDBC API has two parts: an application-level interface used by the application to
access a database, and a service provider interface to attach a JDBC driver to the J2EE
platform.

Java Servlet 2.3

Java Servlet technology lets you define HTTP-specific servlet classes. A servlet class
extends the capabilities of servers that host applications accessed by way of a
request-response programming model. Although servlets can respond to any type of
request, they are commonly used to extend the applications hosted by web servers.
For more information on servlets, see

JavaServer Pages 1.2

JavaServer Pages (JSP) technology lets you put snippets of servlet code directly into a
text-based document. A JSP page is a text-based document that contains two types of
text: static template data which can be expressed in any text-based format such as
HTML, WML, and XML, and JSP elements that determine how the page constructs
dynamic content.
For more information on JSPs, see

Java Message Service 1.0

The Java Message Service (JMS) API is a messaging standard that allows J2EE
application components to create, send, receive, and read messages. It enables distributed
communication that is loosely coupled, reliable, and asynchronous. By passing messages
asynchronously, a process can be offline when a message is initially sent and respond to
messages whenever it is convenient.

Java Transaction API 1.0 and Java Transaction Service

A transaction is a unit of work that makes a set of guarantees about its execution. For
example, one guarantee is that any code executing within the scope of a transaction is all
executed or not executed at all. Transactions are required to maintain a consistent system
state. They allow multiple users to modify the same data, yet each is isolated from the
others.
The J2EE architecture provides a default auto commit to handle transaction commits
and rollbacks. An auto commit means other applications 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 use the
34 Chapter 3 Introduction to J2EE
Chapter 4, "Using Servlets and JSP" on page
Chapter 4, "Using Servlets and JSP" on page
37.
37.