Section 2: Request

2.1 Please describe the proposed Specification:

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.)

javax.deployment

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?

No.

2.9 Are there any internationalization or localization issues?

No.

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.