Datasheet

Part I ✦ Introduction

J2EE 1.4 has dramatically changed that with the introduction of XML-RPC, JAXR,

SAAJ, and modifications within the Enterprise JavaBeans (EJB) specification, as

well as with the manner in which new libraries are deployed. XML and support for

Web services are now an integral part of J2EE, providing another level of abstrac-

tion for the decoupling of systems.

In addition, J2EE 1.4 has improved tools support via the J2EE Management and J2EE

Deployment APIs, and many of the other individual APIs have been enhanced as

well. The following chapters will discuss the various APIs and their capabilities in

greater detail.

Looking toward the Future of J2EE

Java has progressed incredibly since its inception, as has J2EE. While the needs of

today and those of the near future are being met by the current release of J2EE, it

is not complete, nor will it ever be. Like all enterprise systems, J2EE is constantly

evolving.

Some of the innovations planned for the future are an XML data-binding API,

enhanced security APIs, support for JDBC RowSets, and more. For a full list of

potential future enhancements, review “Future Directions” in the specification

document. Alternatively, you can follow the Java Community Process, which is

discussed next.

Understanding the Java

Community Process (JCP)

The JCP is an initiative similar to a standardization body, put in place by Sun to

allow for an unbiased approach to the development of Java. While it is not an official

standards body, it is open to the public. All the Java APIs, along with the various

distributions (J2EE, J2SE, and J2ME), are covered with the JCP.

Generally, the process works as follows:

1. A member (or group of members) within the JCP submits a Java Specification

Request (JSR) which requests either a new specification or modifications to

an existing one.

2. Following the acceptance of the JSR by the JCP, an expert group is formed

and specification development begins.

3. Final acceptance of the specification is made via a vote by an executive

committee.

c539663 ch01.qxd 7/25/03 9:13 AM Page 14