The Java Community Process(SM) Program - JSRs: Java Specification Requests - detail JSR# 318

E-Mail Address: marina.vatkina@oracle.com

Telephone Number: +1 408 276 5637

Fax Number: -

Maintenance Lead Member: Oracle America, Inc.

Maintenance Lead: Linda Demichiel

E-Mail Address: linda.demichiel@oracle.com

Telephone Number: 1 408 276 7057

Fax Number: -

Original Java Specification Request (JSR)

Identification | Request | Contributions

Section 1. Identification

Submitting Member: SUN Microsystems

Name of Contact Person: Kenneth Saks

E-Mail Address: kenneth.saks@sun.com

Telephone Number: +1 703 229 4304

Fax Number: +1 408 276 7191

Specification Lead: Kenneth Saks

E-Mail Address: kenneth.saks@sun.com

Telephone Number: +1 703 229 4304

Fax Number: +1 408 276 7191

Initial Expert Group Membership:

TBD

Supporting this JSR:

# Tmax Soft
# BEA
# JBoss (Red Hat Middleware LLC)
# Diamelle Technologies
# Oracle
# Pramati
# SAP
# Hani Suleiman
# Sybase
# Apache
# OW2 Consortium
# Charlton Barreto
# Felipe Leme

Section 2: Request

2.1 Please describe the proposed Specification:

Enterprise JavaBeans is an architecture for the development and deployment of component-based business applications. Applications written using the Enterprise JavaBeans architecture are scalable, transactional, and multi-user secure.

The Enterprise JavaBeans 3.0 specification focused on bringing ease-of-use to the EJB API. The purpose of the Enterprise JavaBeans 3.1 specification is to further simplify the EJB architecture by reducing its complexity from the developer's point of view, while also adding new functionality in response to the needs of the community.

The focus will be on the core session bean and message-driven bean component models and their client API. Although the Java Persistence API was developed within EJB 3.0, it will evolve under a separate JSR rather than within EJB 3.1.

Aspects that should be considered by the Expert Group for inclusion in this work include, but are not limited to, the following:

• Removal of the requirement for a separate local business interface.
• Support for direct use of EJBs in the servlet container, including simplified packaging options.
• Singleton beans.
• Support for asynchronous session bean invocation.
• Support for stateful web services via stateful session bean web service endpoints.
• Specification of concurrency options for stateful session beans.
• Application-level callback notifications, including for container initialization and shutdown.
• EJB Timer Service enhancements to support cron-like scheduling, deployment-time timer creation, and stateful session bean timed objects.
• An ejb-jar level component environment to simplify the specification of shared dependencies among components.

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

The target platform is Java EE.

2.3 The Executive Committees would like to ensure JSR submitters think about how their proposed technology relates to all of the Java platform editions. Please provide details here for which platform editions are being targeted by this JSR, and how this JSR has considered the relationship with the other platform editions.

The Enterprise JavaBeans architecture is specifically designed for the Java EE platform environment.

Should this JSR be voted on by both Executive Committees?

No. It should be voted on by the Java SE / EE Executive Committee only.

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

The goal of the proposed specification is to address the needs of the Java community by augmenting the functionality of Enterprise JavaBeans to address requests received from the Java community for additional features.

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

See 2.5 above. These new features are specific to the Enterprise JavaBeans architecture, which does not yet provide them.

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

See above.

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

The API specification will continue to use the javax.ejb package.

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

No.

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

No.

2.11 Are there any internationalization or localization issues?

No.

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

No.

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

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

The primary means of communication will be email and conference calls. Face-to-face meetings will be scheduled if needed.

2.15 It is important to the success of the community and each JSR that the work of the Expert Group be handled in a manner which provides the community and the public with insight into the work the Expert Group is doing, and the decisions that the Expert Group has made. The Executive Committees would like to ensure Spec Leads understand the value of this transparency and ask that each JSR have an operating plan in place for how their JSR will address the involvement of the community and the public. Please provide your plan here, and refer to the Spec Lead Guide for a more detailed description and a set of example questions you may wish to answer in your plan.

The Expert Group will publish early drafts for review by the community at convenient points during the development of the specification. The Expert Group will solicit feedback from the community via public fora(e.g., public presentations, blogs, and other online postings).

2.16 Please describe how the RI and TCK will de delivered, i.e. as part of a profile or platform edition, or stand-alone, or both. Include version information for the profile or platform in your answer.

Sun Microsystems will deliver a Reference Implementation (RI) and Technology Compatibility Kit (TCK) as part of Java EE 6.

2.17 Please state the rationale if previous versions are available stand-alone and you are now proposing in 2.13 to only deliver RI and TCK as part of a profile or platform edition (See sections 1.1.5 and 1.1.6 of the JCP 2 document).

N/A

2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.

Pursuant to Section 2.2.1 of the Java Community Process version 2.6, the following is a summary of Sun's anticipated principal license terms and conditions for the JSR, Enterprise JavaBeans (EJB), version 3.1. The business terms for EJB 3.1 have not changed from those for EJB 3.0 and they impose no new restrictions.

The EJB 3.1 Technology Compatibility Kit (TCK) will be available as part of the Java EE 6 Compatibility Test Suite (CTS). The EJB 3.1 Reference Implementation (RI) will be available as part of the Java EE 6 RI.

Non-Commercial Use

Commercial Use

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.

The EJB 3.0 Specification (JSR 220)
http://jcp.org/eng/jsr/detail?id=220

Java Platform, Enterprise Edition Specification Version 5
http://jcp.org/en/jsr/detail?id=244

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

The Simplified API specification and Core API specification from JSR 220 will be the starting point for this work.