Find JSRs
Submit this Search


Ad Banner
 
 
 
 

Summary  |  Proposal  |  Detail (Summary & Proposal)
JSRs: Java Specification Requests
JSR 151: JavaTM 2 Platform, Enterprise Edition 1.4 (J2EE 1.4) Specification

Stage Access Start Finish
Maintenance Draft Review Download page 24 Mar, 2004 26 Apr, 2004
Final Release Download page 24 Nov, 2003  
Final Approval Ballot View results 28 Oct, 2003 11 Nov, 2003
Proposed Final Draft 3 Download page 15 Apr, 2003  
Proposed Final Draft 2 Download page 12 Nov, 2002  
Proposed Final Draft Download page 21 Aug, 2002  
Public Review Download page 18 Jul, 2002 17 Aug, 2002
Community Draft Ballot View results 25 Jun, 2002 01 Jul, 2002
Community Review Login page 29 May, 2002 01 Jul, 2002
Expert Group Formation   23 Oct, 2001  
JSR Review Ballot View results 09 Oct, 2001 22 Oct, 2001
Status: Maintenance
JCP version in use: 2.5
Java Specification Participation Agreement version in use: 2.0


Description:
This JSR is to develop J2EE 1.4, the next release of the Java 2 Platform, Enterprise Edition.

Please direct comments on this JSR to the Spec Lead(s)
Team

Specification Leads
  Mark Hapner Sun Microsystems, Inc.
Star Spec Lead Bill Shannon Sun Microsystems, Inc.
Expert Group
  Avedal, Karl Barreto, Charlton BEA Systems
  Fesq, B.J. IBM iPlanet
  Kohen, Elika S. Lutris Technologies Macromedia, Inc.
  Monson-Haefel, Richard Novell, Inc. Oracle
  Persistence Software Inc. Pramati Technologies Progress Software
  SAP AG SeeBeyond Technology Corp. Sun Microsystems, Inc.

Original Java Specification Request (JSR)

Identification | Request | Contributions

Section 1. Identification

Submitting Member: Sun Microsystems, Inc.

Name of Contact Person: Bill Shannon

E-Mail Address: bill.shannon@sun.com

Telephone Number: +1 408 276 7280

Fax Number: +1 408 276 7191


Specification Leads:
Bill Shannon
Mark Hapner

E-Mail Addresses:
bill.shannon@sun.com
mark.hapner@sun.com

Telephone Numbers:
+1 408 276 7280
+1 408 276 7105

Fax Number: +1 408 276 7191


Supporting this JSR:

BEA
Borland
Compaq
Fujitsu
IBM
IONA
IronFlare AB (Orion Application Server)
Oracle
SilverStream



Section 2: Request

2.1 Please describe the proposed Specification:

This JSR is to develop J2EE 1.4, the next release of the Java 2 Platform, Enterprise Edition, targeted to ship in the second half of 2002.

The major theme for the next version of J2EE is web services. The clear message we've gotten from J2EE vendors and users is that the J2EE platform must evolve quickly to provide support for web services, initially using SOAP/HTTP as the primary protocol. This protocol support is being defined in other JSRs (enumerated below). We propose that:

  • J2EE 1.4 will define the J2EE component model, deployment, packaging, and container requirements for J2EE components that use JAX-RPC and JAXM to implement web service endpoints.
  • J2EE 1.4 will define the J2EE component model, deployment, packaging, and container requirements for J2EE components that use JAX-RPC and JAXM to access web service endpoints.
  • J2EE 1.4 will define the J2EE component model, deployment, packaging, and container requirements for use of JAXR to access web service registries.

J2EE 1.4 will also deliver on work in progress to improve the support for J2EE tools, and will provide minor enhancements to existing APIs as required.

This JSR will not itself define any new APIs, rather it will enumerate APIs defined in other JSRs or through the JCP maintenance process. We propose to include the following new APIs or API revisions in J2EE 1.4 in support of the above goals:

  • J2EE 1.4 is the Enterprise Edition of version 1.4 of the Java platform, and thus will be built on J2SE 1.4.

    The following JSRs provide the basic web services support for J2EE.

  • JSR-109 (Web Services)
  • JSR-101 (JAX-RPC)
  • JSR-67 (JAXM)
  • JSR-93 (JAXR)

    The following JSRs provide new capabilities to J2EE 1.4.

  • JSR-77 (management)
  • JSR-88 (deployment API)
  • JSR-115 (J2EE Authorization SPI)
  • JSR-56 (JNLP)

    The following JSRs enhance APIs that are in J2EE 1.3.

  • JSR-112 (J2EE Connector Architecture 2.0)
  • JSR-152 (JSP 1.3)
  • JSR-154 (Servlet 2.4)
  • JSR-153 (EJB 2.1)
  • JSR-9XX (JAXP 1.2 - XML Schema support)
  • JSR-9XX (JMS 1.1 - queue/topic unification)

We believe that it is critical to deliver a J2EE platform with web services support as soon as possible. To be successful, the target feature set will need to be carefully managed. Very few technologies that aren't already well defined will be able to be included, and such new technologies will need to be tightly focused on the essential items necessary for web services support. Future J2EE releases will expand on this basic web services support and will provide support in other areas as well.

Some of the JSRs listed above are near completion, others are just starting. Spec leads for all included JSRs will need to remain focused on the goal of delivering web services support in J2EE 1.4 as soon as possible. Those that complete in time will be included in J2EE 1.4. Those that fail to complete in time may not be included. In the rare case that a critical JSR fails to complete in time or fails to define the level of web services support required by J2EE, this JSR may define a minimal set of such features as needed to successfully deliver on the goal of web services support.

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

This specification defines the next release of the J2EE Platform.

2.3 What need of the Java community will be addressed by the proposed specification?

J2EE 1.4 will extend J2EE 1.3 and build on J2SE 1.4 with a full set of facilities for the development, deployment and execution of multi-tier, server-centric web service applications. J2EE 1.4 will also enhance the support for tools that work with J2EE products, including management and deployment tools.

2.4 Why isn't this need met by existing specifications?

While J2EE 1.3 defines the basic mechanisms that can be used to build web services of many kinds, it lacks any requirements for the new web service protocols, such as SOAP/HTTP. In addition, J2EE 1.3 defines no APIs for tools to use to interact with a J2EE product. Consequently, J2EE vendors and tool vendors that offer support in these areas must necessarily do so using vendor-specific architectures.

2.5 Please give a short description of the underlying technology or technologies:

A detailed description of J2EE 1.3 functionality can be found in the J2EE 1.3 Specification, http://java.sun.com/j2ee/download.html.

2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

The J2EE Platform itself does not require a package name. All of its requirements are reflected in the packages of its constituent Java APIs.

2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?

No.

2.8 Are there any security issues that cannot be addressed by the current security model?

J2EE 1.4 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.4.

In addition, J2EE 1.4 will define Service Provider Interfaces that allow security technology vendors to integrate with J2EE application servers.

2.9 Are there any internationalization or localization issues?

J2EE uses the I18N support in J2SE.

2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?

Other than the J2EE specification itself and the new versions of its constituent component models and access APIs, J2EE 1.4 should not require other existing specifications to be revised.

2.11 Please describe the anticipated schedule for the development of this specification.

We hope to deliver the final specification, reference implementation, and TCK in the second half of 2002. This implies that the specification must reach Proposed Final Draft early in the first half of 2002.

2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.

The primary means of communication will be email, with conference calls and face-to-face meetings scheduled as needed.





Section 3: Contributions

3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

Java 2 Platform, Enterprise Edition Specification Version 1.3, and related specifications
http://java.sun.com/j2ee/docs.html#specs

Java 2 Platform, Standard Edition, v1.4 API Specification
http://java.sun.com/j2se/1.4/docs/api/index.html

JSR-109 Implementing Enterprise Web Services
http://jcp.org/jsr/detail/109.jsp

JSR-101 Java APIs for XML based RPC
http://jcp.org/jsr/detail/101.jsp

JSR-67 Java APIs for XML Messaging 1.0
http://jcp.org/jsr/detail/67.jsp

JSR-93 Java API for XML Registries 1.0 (JAXR)
http://jcp.org/jsr/detail/93.jsp

JSR-77 J2EE Management
http://jcp.org/jsr/detail/77.jsp

JSR-88 J2EE Application Deployment
http://jcp.org/jsr/detail/88.jsp

JSR-115 Java Authorization Service Provider Contract for Containers
http://jcp.org/jsr/detail/115.jsp

JSR-56 Java Network Launching Protocol and API
http://jcp.org/jsr/detail/56.jsp

JSR-112 J2EE Connector Architecture 2.0
http://jcp.org/jsr/detail/112.jsp

JSR-152 JSP 1.3
http://jcp.org/jsr/detail/152.jsp

JSR-154 Servlet 2.4
http://jcp.org/jsr/detail/154.jsp

JSR-153 EJB 2.1
http://jcp.org/jsr/detail/153.jsp

JSR-9XX JAXP 1.2 - XML Schema support
http://jcp.org/jsr/detail/9XX.jsp

JSR-9XX JMS 1.1 - queue/topic unification
http://jcp.org/jsr/detail/9XX.jsp

3.2 Explanation of how these items might be used as a starting point for the work.

These specifications will be the basis for J2EE 1.4.