 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 345: Enterprise JavaBeansTM 3.2
The following information has been updated since the original proposal on the dates shown: 2014.07.30: The Maintenance Lead has changed from Marina Vatkina to Linda DeMichiel. Maintenance Lead Member: Oracle America, Inc. Maintenance Lead: Linda Demichiel E-Mail Address: linda.demichiel Telephone Number: 1 408 276 7057 Fax Number: - 2013.03.05:2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.
2.13 Please describe the anticipated schedule for the development of this specification.
Apr 2011 Expert Group formed
2012.02.02: Original Java Specification Request (JSR)
Identification |
Request |
Contributions
Section 1. Identification Submitting Member: Oracle Corporation Name of Contact Person: Linda DeMichiel E-Mail Address: linda.demichiel Telephone Number: +1 408 276 7057 Fax Number: +1 408 276 4185 Specification Leads: Linda DeMichiel, Marina Vatkina E-Mail Address: linda.demichiel Telephone Number: +1 408 276 7057, +1 408 276 5637 Fax Number: +1 408 276 4185 Initial Expert Group Membership: TBD Supporting this JSR: Adam Bien Section 2: Request
2.1 Please describe the proposed Specification:Enterprise JavaBeans (EJB) 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 was focused on bringing ease-of-use to the EJB API. The Enterprise JavaBeans 3.1 specification further simplified the EJB architecture from the developer's point of view, while also adding significant new functionality in response to the needs of the community. The goal of Enterprise JavaBeans 3.2 is to consolidate these advances and to continue to simplify the EJB architecture as well as to provide support for the Java EE platform-wide goal of further enabling cloud computing. The scope of EJB 3.2 is intended to be relatively constrained in focusing on these goals. Aspects that are planned to be considered in this work include, but are not necessarily limited to, the following:
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 3.2 architecture is expected to be included as a required part of the Java Platform, Enterprise Edition version 7. Aligning the timeline of this JSR with that of Java EE 7 may therefore impact the scope of the Enterprise JavaBeans 3.2 release. Features that may not be able to be addressed in Enterprise JavaBeans 3.2 due to time constraints may become candidates for a future release. 2.4 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 further simplifying Enterprise JavaBeans from the perspective of the developer and aligning it to meet the evolving needs of the Java EE 7 Platform. 2.6 Why isn't this need met by existing specifications?See above. 2.7 Please give a short description of the underlying technology or technologies:See above. A detailed description of the EJB technology can be found in the EJB 3.1 specification, http://jcp.org/en/jsr/summary?id=318. 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, javax.ejb.embeddable, and javax.ejb.spi packages. 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.
Note that this section of the JSR has been updated since this original proposal. 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 Provide detailed answers to the transparency checklist, making sure to include URLs as appropriate.
2.16 Please describe how the RI and TCK will be 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.Oracle Corporation will deliver a Reference Implementation (RI) and Technology Compatibility Kit (TCK) as part of Java EE 7. 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 the full text of the licenses that will apply to your Final Release Specification, Reference Implementation and Technology Compatibility Kit, or provide links to the same.Note that this information has been updated since this original proposal. Specification license 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.Enterprise JavaBeans specification, http://jcp.org/en/jsr/detail?id=318 3.2 Explanation of how these items might be used as a starting point for the work.The Enterprise JavaBeans API as defined by JSR-318 will be the starting point for this work. Experience with existing implementations and vendor extensions to the Enterprise JavaBeans architecture as defined by JSR-318 will be considered when evaluating new functionality. |
