Find JSRs
Submit this Search

Ad Banner

Summary  |  Proposal  |  Detail (Summary & Proposal)
JSRs: Java Specification Requests
JSR 88: JavaTM EE Application Deployment

Stage Access Start Finish
Maintenance Release 2 Download page 07 Jun, 2006  
Maintenance Draft Review 3 Download page 31 Jan, 2006 06 Mar, 2006
Maintenance Draft Review 2 Download page 28 Oct, 2005 28 Nov, 2005
Maintenance Release Download page 24 Nov, 2003  
Maintenance Draft Review Download page 05 Sep, 2002 07 Oct, 2002
Final Release Download page 19 Jul, 2002  
Final Approval Reconsideration Ballot View results 04 Jun, 2002 17 Jun, 2002
Final Approval Ballot Failed   07 May, 2002  
Final Approval Ballot View results 23 Apr, 2002 06 May, 2002
Proposed Final Draft Download page 13 Feb, 2002  
Public Review Download page 19 Dec, 2001 18 Jan, 2002
Community Draft Ballot View results 06 Nov, 2001 12 Nov, 2001
Community Review Login page 10 Oct, 2001 12 Nov, 2001
Expert Group Formation   24 Oct, 2000 07 Nov, 2000
JSR Review Ballot View results 10 Oct, 2000 23 Oct, 2000
Status: Maintenance
JCP version in use: 2.6
Java Specification Participation Agreement version in use: 2.0

This specification provides a complete description of the APIs required by the J2EE platform to enable development of platform-independent deployment tools.

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

Specification Leads
  Gerald Ingalls Oracle
Expert Group
  BEA Systems IBM IBM/Websphere
  iPlanet Oracle Progress Software
  Silverstream Software Skylight Systems, Inc. Sun Microsystems, Inc.
  Sybase WebGain

Updates to the Original JSR

The following updates were made to the original request:

Maintenance Lead:Jerome Dochez
E-Mail Address:
Telephone Number: +1 408 276 7062
Fax Number: +1 408 276 7191

Original Java Specification Request (JSR)

Identification | Request | Contributions

Section 1. Identification

Submitting Member: Sun Microsystems, Inc

Name of Contact Person: Rebecca Searls

E-Mail Address:

Telephone Number: (781) 442-0462

Fax Number: (781) 443-1610

Specification Lead: Rebecca Searls

E-Mail Address:

Telephone Number: (781) 442-0462

Fax Number: (781) 443-1610

Initial Expert Group Membership:
(Please provide company or organization names. Note that expert group members must have signed the JSPA.)

Skylight Systems
Aaron Mulder

Mark Romano

George Finklang

Gerald Ingalls

Helen Herold

Mark Spotswood>

Michael Fraenkel

Verge Technologies Group Inc
Jason Westra

David Hayes

Byron Nevins

Section 2: Request

2.1 Please describe the proposed Specification:

This specification defines standard APIs that will enable any deployment tool that uses the deployment APIs to deploy any assembled application onto a J2EE compatible platform.

The API will address the three-stage deployment process:

  • Installation - move the properly packaged components to the server
  • Configuration - the resolution of all external dependencies declared by the application
  • Undeployment - removal of the application from the server

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

Java 2 Platform Enterprise Edition

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

J2EE Product Providers currently implement their own proprietary deployment interface to their server because there is no standard deployment API. This makes it cumbersome for companies that host heterogeneous J2EE environments to deploy an application across multiple J2EE environments, because they must run the designated deploy tool for a given server. A standard deployment API will enable any J2EE application to be deployed by any deployment tool that uses the deployment APIs onto any J2EE compatible environment.

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

The Java 2 Platform Enterprise Edition Specification specifies a deployment file format and static deployment information descriptors. It does not, however, define a standard API for gathering dynamic deployment information that applies to application installation into the server, application configuration, or undeployment.

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

The Deployment Specification will support the existing deployment file format and static deployment information descriptors. In addition it will provide an interface for discovering additional information from J2EE servers which implement it. The interface will also enable tools to collect vendor specific dynamic information for installing, configuring and undeploying J2EE applications on the server. The API will encapsulate the common functions of different vendors' deployment process with a standardized Java interface.

No dependency on Java visual tools for constructing and deploying J2EE applications will be assumed by this API.

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


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


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


2.9 Are there any internationalization or localization issues?


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

Future releases of the Java 2 Enterprise Edition Specification may require revision in the area of deployment.

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

Community Draft October 2001
Public Draft December 2001
Proposed Final Draft February 2002
Final Release Aligned with J2EE 1.4 Platform Spec Final Release

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

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

The J2EE specification defines the deployment requirements, but does not define specific APIs.