JSRs: Java Specification Requests
JSR 58: JavaTM 2 Platform, Enterprise Edition 1.3 Specification
Section 1: Identification
Submitting Participant: Sun Microsystems, Inc.
Name of Contact Person: Mark Hapner and Bill Shannon
Telephone Number: +1 408 343 1609 and +1 408 343 1980
List of other Participants who endorse this JSR:
Projected expert group will include experts from:
The partners that participated in the definition of J2EE 1.2 have expressed strong interest in participating in the expert group for J2EE 1.3.
Section 2: Request
This JSR is to develop J2EE 1.3, the next release of the Java 2 Platform, Enterprise Edition, targetted to ship in 2000.
This JSR will not itself define any new APIs, rather it will enumerate APIs defined in other JSRs or through the JCP maintenance process.
A major theme for the next version of J2EE will be to include technologies requested for J2EE 1.2, but which were not ready in time for that release.
The JSR expert group will define a specification consisting of a
target feature and API set for J2EE 1.3. This target list will be
further refined during participant review and public review and
will become the target feature set for the J2EE 1.3 release. The
goal is that the J2EE 1.3 release will include this full target set,
but depending on implementation and API design schedules some
items may be deferred to a later release if they are unable to
make the release schedule for J2EE 1.3. The final specification
will reflect the final J2EE 1.3 deliverables.
This specification defines the next release of the J2EE Platform.
J2EE 1.3 will extend J2SE 1.3 with a full set of facilities for the development, deployment and execution of multi-tier, server-centric applications. These facilities include Enterprise JavaBeansTM, Java Server Pages, and Servlet component models; and JDBC, JavaMail, JMS, and the new Connector APIs for accessing existing enterprise services.
The purpose of J2EE 1.3 is to address a number of open areas in J2EE 1.2 where further support has been requested by the J2EE partners and the public.
The areas we intend to address include, but are not limited to, those listed below. This represents our initial proposal for the contents of J2EE 1.3, which will be refined by the expert group in the usual manner.
The following technology areas, while important to J2EE, are unlikely to meet the schedule requirements of J2EE 1.3 and may be deferred to a future release.
2.3 Explanation of why the need isn't met by existing specifications
As discussed above, these areas are largely unspecified in J2EE
1.2. Consequently, J2EE server vendors and tool vendors that offer
support in these areas must necessarily do so using vendor-specific
This extension and revision to the J2EE 1.2 specification is
intended to address these needs in the ways described above.
A detailed description of J2EE 1.2 functionality can be found in the
J2EE 1.2 Specification, http://java.sun.com/j2ee/download.html.
The J2EE Platform itself does not require a package name. All of its
requirements are reflected in the packages of its constituent Java APIs.
J2EE 1.3 addresses mechanisms and policies required for secure usage of
its constituent component models and access APIs. These mechanisms must
be compatible with the security facilities of J2SE 1.3.
J2EE uses the I18N support in J2SE.
In the absence of this specification, it is highly likely that J2EE container providers will develop container-specific mechanisms to support the facilities listed in section 2.2 of this document. If this occurs it will limit the portability of J2EE applications and tools.
Since J2EE is a critically important foundation for developing
enterprise applications, the vendors delivering J2EE products require
that J2EE 1.3 be a stable, incremental and timely evolution of J2EE 1.2.
Failure to insure backward compatibility of J2EE 1.2 applications or
failure to deliver J2EE 1.3 in a timely manner could negatively effect
continued support and use of J2EE.
A primary goal of J2EE is backward compatibility of J2EE applications.
All J2EE 1.2 applications that stay within the bounds of the J2EE 1.2
Platform specification must be compatible with J2EE 1.3.
Other than the J2EE specification itself and the new versions of its
constituent component models and access APIs, J2EE 1.3 should not
require other existing specifications to be revised.
3.1 List of relevant existing documents:
Java 2 Platform, Enterprise Edition Specification Version 1.2
Java 2 Platform, Enterprise Edition Technical Overview
Java 2 Platform, Standard Edition, v1.2.2 API Specification
Enterprise JavaBeans Specification, Version 1.1
Enterprise JavaBeans to CORBA Mapping, Version 1.1
JavaServer Pages Specification, Version 1.1
Java Servlet Specification, Version 2.2
JDBC 2.0 API
JDBC 2.0 Standard Extension API
Java Naming and Directory Interface 1.2 Specification
Java Message Service, Version 1.0.2
Java Transaction API, Version 1.0.1
Java Transaction Service, Version 0.95
JavaMail API Specification Version 1.1
JavaBeans Activation Framework Specification Version 1.0.1
IDL-To-Java Mapping Specification, Object Management Group
Java-To-IDL Mapping Specification, Object Management Group
The Java 2 Platform, Enterprise Edition Application Programming Model
The SSL Protocol, Version 3.0
JSR-000005 XML Standard Extension Specification
JSR-000016 J2EE[tm] Connector Specification -
JSR-000019 Enterprise JavaBeans[tm] 2.0 Specification
These specifications (with the exception of the listed JSRs) are the basis for J2EE 1.2. These or their subsequent versions will be the basis for J2EE 1.3.
The functionality of the listed JSRs are expected to define new requirements for J2EE 1.3.