Addison wesley java 2 platform enterprise edition platform and component specifications may 2000 ISBN 0201704560 (1)

Edition: Platform and Components Specifications defines the architecture for developing applications with J2EE.. This volume includes: JavaTM 2 Platform, Enterprise Edition Specification

Edition: Platform and Components Specifications defines the architecture

for developing applications with J2EE This volume includes:

Java(TM) 2 Platform, Enterprise Edition Specification, version 1.2 This specification defines the initial release of the J2EE platform It

JavaServer Pages(TM), Enterprise JavaBeans(TM), and other

technologies It specifies application access to services such as JDBC(TM), Java Transaction API, JavaMail(TM), CORBA

connectivity, and others It also discusses J2EE policies regarding application deployment and security.

Enterprise JavaBeans(TM) Specification, version 1.1

Enterprise JavaBeans technology provides the standard middle-tier components in the J2EE model This technology provides simplified support for transaction management and remote object access, and

it frees enterprise developers to focus on the business logic of their applications Version 1.1 of the specification includes a number of enhancements, including mandatory entity beans and XML

deployment descriptors.

Java(TM) Servlet Specification, version 2.2

side behaviors in web applications based on the Java programming language As part of the J2EE specifications, servlets technology supports development of dynamic web content for e-commerce and other enterprise applications.

Java Servlets technology defines a standard for developing server-JavaServer Pages(TM) Specification, version 1.2

The JavaServer Pages (JSP) technology simplifies the development and deployment of interactive web applications Using an extensible markup language based on HTML and the Java programming

language, JSP defines a server-side mechanism to allow content experts greater freedom in creating and displaying dynamic web content.

Developed with the input of a wide range of industry experts, these

specifications define a new standard for resolving many complex issues related to developing, deploying, and managing multi-tier enterprise applications.

Authorization Requirements Section J2EE.3.6.

Deployment Requirements Section J2EE.3.7.

System Administration Tools

Section J2EE.6.11.

Section J2EE.6.12.

JavaBeans™ Activation Framework 1.0 Requirements Chapter J2EE.7.

Section SRV.P.3.

Other Java™ Platform Specifications Section SRV.P.4.

Relationship to Java 2 Enterprise Edition Section SRV.1.6.

Section SRV.4.7.

Temporary Working Directories Chapter SRV.5.

Headers

Section SRV.5.4.

Request Path Elements Section SRV.5.5.

Path Translation Methods Section SRV.5.6.

Sessions

Section SRV.7.1.

Session Tracking Mechanisms Section SRV.7.2.

Section SRV.9.3.

Distinction Between Representations Section SRV.9.4.

Replacing a Web Application

Section SRV.9.8.

Who Should Read This Document Section JSP.P.2.

Section JSP.2.4.

Quoting and Escape Conventions Section JSP.2.5.

Section JSP.7.1.

Why an XML Representation

The Servlet for the Compiled JSP Page Section JSP.C.4.

The Web Application Descriptor

Section JSP.C.5.

The WAR for the Compiled JSP Page Appendix JSP.D.

Changes Between 1.1 PR1 and PR2 Section JSP.E.3.

Changes Between 1.1 PD1 and PR1 Section JSP.E.4.

Changes Between 1.0 and 1.1 PD1 Enterprise JavaBeans™ Specification, v1.1 (EJB) Chapter EJB.1.

Section EJB.6.7.

Object Interaction Diagrams for a Stateful Session Bean Section EJB.6.8.

Stateless Session Beans

Section EJB.6.9.

Object Interaction Diagrams for a Stateless Session Bean Section EJB.6.10.

Section EJB.12.1.

Overview and Concepts

Section EJB.12.2.

Section EJB.15.2.

Bean Provider's Responsibilities Section EJB.15.3.

Application Assembler's Responsibilities Section EJB.15.4.

Deployer's Responsibilities

Section EJB.15.5.

EJB Architecture Client Responsibilities Section EJB.15.6.

EJB Container Provider's Responsibilities Section EJB.15.7.

System Administrator's Responsibilities Chapter EJB.16.

Application Assembler's Responsibility Section EJB.16.4.

Container Provider's Responsibilities Section EJB.16.5.

Deployment Descriptor DTD

Section EJB.16.6.

Deployment Descriptor Example Chapter EJB.17.

Responsibilities of EJB Architecture Roles Section EJB.19.1.

Bean Provider's Responsibilities

Section EJB.19.2.

Application Assembler's Responsibilities Section EJB.19.3.

EJB Container Provider's Responsibilities Section EJB.19.4.

Deployer's Responsibilities

Section EJB.19.5.

System Administrator's Responsibilities Section EJB.19.6.

Client Programmer's Responsibilities Chapter EJB.20.

Enterprise JavaBeans™ API Reference Section EJB.20.1.

Package javax.ejb

Section EJB.20.2.

Package javax.ejb.deploymentChapter EJB.21.

Related Documents

Appendix EJB.A.

Section EJB.B.6.

javax.transaction.UserTransaction Versusjavax.jts.UserTransaction

Sun hereby grants you a fully-paid, non-exclusive, non-transferable, worldwide, limited license (withoutthe right to sublicense), under Sun's intellectual property rights that are essential to practice the

Specification, to internally practice the Specification solely for the purpose of creating a clean roomimplementation of the Specification that: (i) includes a complete implementation of the current version ofthe Specification, without subsetting or supersetting; (ii) implements all of the interfaces and functionality

of the Specification, as defined by Sun, without subsetting or supersetting; (iii) includes a completeimplementation of any optional components (as defined by Sun in the Specification) which you choose

to implement, without subsetting or supersetting; (iv) implements all of the interfaces and functionality ofsuch optional components, without subsetting or supersetting; (v) does not add any additional

packages, classes or interfaces to the "java.*" or "javax.*" packages or subpackages (or other packagesdefined by Sun); (vi) satisfies all testing requirements available from Sun relating to the most recentlypublished version of the Specification six (6) months prior to any release of the clean room

implementation or upgrade thereto; (vii) does not derive from any Sun source code or binary codematerials; and (viii) does not include any Sun source code or binary code materials without an

appropriate and separate license from Sun The Specification contains the proprietary information ofSun and may only be used in accordance with the license terms set forth herein This license willterminate immediately without notice from Sun if you fail to comply with any provision of this license.Upon termination or expiration of this license, you must cease use of or destroy the Specification

DISCLAIMER OF WARRANTIES

THE SPECIFICATION IS PROVIDED "AS IS" SUN MAKES NO REPRESENTATIONS OR

WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES

OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT THATTHE CONTENTS OF THE SPECIFICATION ARE SUITABLE FOR ANY PURPOSE OR THAT ANY

THE SPECIFICATION COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICALERRORS CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION THEREIN; THESECHANGES WILL BE INCORPORATED INTO NEW VERSIONS OF THE SPECIFICATION, IF ANY.SUN MAY MAKE IMPROVEMENTS AND/OR CHANGES TO THE PRODUCT(S) AND/OR THE

PROGRAM(S) DESCRIBED IN THE SPECIFICATION AT ANY TIME Any use of such changes in theSpecification will be governed by the then-current license for the applicable version of the Specification

LIMITATION OF LIABILITY

TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BELIABLE FOR ANY DAMAGES, INCLUDING WITHOUT LIMITATION, LOST REVENUE, PROFITS ORDATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES,HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF ORRELATED TO ANY FURNISHING, PRACTICING, MODIFYING OR ANY USE OF THE

SPECIFICATION, EVEN IF SUN AND/OR ITS LICENSORS HAVE BEEN ADVISED OF THE

POSSIBILITY OF SUCH DAMAGES

You will indemnify, hold harmless, and defend Sun and its licensors from any claims arising or resultingfrom: (i) your use of the Specification; (ii) the use or distribution of your Java application, applet and/orclean room implementation; and/or (iii) any claims that later versions or releases of any Specificationfurnished to you are incompatible with the Specification provided to you under this license

RESTRICTED RIGHTS LEGEND

U.S Government: If this Specification is being acquired by or on behalf of the U.S Government or by aU.S Government prime contractor or subcontractor (at any tier), then the Government's rights in theSoftware and accompanying documentation shall be only as set forth in this license; this is in

accordance with 48 C.F.R 227.7201 through 227.7202-4 (for Department of Defense (DoD)

acquisitions) and with 48 C.F.R 2.101 and 12.212 (for non-DoD acquisitions)

REPORT

You may wish to report any ambiguities, inconsistencies or inaccuracies you may find in connection withyour use of the Specification ("Feedback") To the extent that you provide Sun with any Feedback, youhereby: (i) agree that such Feedback is provided on a non-proprietary and non-confidential basis, and(ii) grant Sun a perpetual, non-exclusive, worldwide, fully paid-up, irrevocable license, with the right tosublicense through multiple levels of sublicensees, to incorporate, disclose, and use without limitationthe Feedback for any purpose related to the Specification and future versions, implementations, andtest suites thereof

The publisher offers discounts on this book when ordered in quantity for special sales For moreinformation, please contact Pearson Education Corporate Sales Division One Lake Street

In the old days (like, 1995) computing servers were only used by a company's employees, i.e., on anintranet Today every company seems to be on the Internet They have an order of magnitude:

customers, suppliers, distributors, and potentially anyone (or anything) with access to their web site.Companies have been forced to move from local client-server or mainframe computing to a new

multitier computing model They have a completely new set of problems in reliability, scalability, security,application deployment, transaction processing, web interface design, and timely software development.This book describes a solution to those problems: Java™ 2 Platform, Enterprise Edition, or J2EE J2EEextends the Java™ 2 Platform, Standard Edition to enable "Write Once Run Anywhere" for multi-tiercomputing It is an industry standard from dozens of companies who are developing J2EE-compliantproducts for their customers

This book is targeted at software developers who are building those products, or who are writing

applications on top of them It is the definitive reference for J2EE and its component models: EnterpriseJavaBeans, servlets, and JavaServer Pages These component models enable the use of Java

technology in web servers and application servers as well as with clients in a distributed computingenvironment

Part I of the book, the J2EE specification, defines the standard This standard enables portability ofsoftware across products from a wide variety of vendors selling J2EE-compliant server products

Parts II and III of the book describe servlets and JavaServer Pages, the web server components for theJ2EE platform Servlets and JavaServer Pages provide standards for extending server functionality andthe generation of dynamic web content Servlets define a simple way to process web server requests,while JavaServer Pages provide a simple way of invoking and embedding Java code in HTML and XMLtemplates

Part IV describes Enterprise JavaBeans, the application server component model for the J2EE platform

In addition to providing a binary standard for portability across products, Enterprise JavaBeans greatlysimplify the development of server code by automating the details of transactions, security, scalability,and other complex aspects of server-side computing They also add value by simplifying the

deployment and customization of components to specific installations This book is a specification and areference manual It defines the J2EE platform For a beginning introduction to J2EE, refer to whitepapers, documentation, and example code at: http://java.sun.com/j2ee/download.html

You may also want to download or purchase Nick Kassem's Designing Enterprise Applications with the Java™ 2 Platform, Enterprise Edition, which provides a programmer's guide to J2EE If you do not have

access to a J2EE-compliant product, a reference implementation of J2EE is available for download atthe same location This implementation is suitable for trying out J2EE prior to investing in a third-partyproduct

History and Acknowledgements

Of course, a foreword to a book like this requires a history of the people behind the project My owninvolvement began in 1995, when I transferred to the JavaSoft division to work on JDBC databaseconnectivity with Graham Hamilton We liked the Java platform because it combined the best features ofmany programming languages we had used in our careers At the time, it was gaining popularity for use

in Internet browsers, but our intuition was that it had wider appeal Indeed, in the years to come, theJava platform proved more popular in distributed computing than anyone could have envisioned in1995

In 1996, Mark Hapner joined us to help with JDBC, and then with a group of application programminginterfaces (APIs) I was calling "enterprise Java." Over the years that followed Mark participated in thedesign of more of the evolving J2EE platform than any other individual, becoming the central architect.Vlada Matena joined us later in 1996, leading the design of a transaction API and then EnterpriseJavaBeans, which became a cornerstone of J2EE Vlada wrote the original summary for a J2EE

specification, which later evolved into Part I of this book, written by Bill Shannon

The Java Web Server project also began in 1996 Through the work of a lot of dedicated people, thisproject eventually culminated in the servlet and JavaServer Pages APIs James Davidson and EduardoPelegri-Llopart most recently led these efforts Along with Brian Behlendorf, Jon Stevens, and others,they pioneered the use of the Apache open source model to provide a widely-adopted implementation

of these APIs Servlets and JavaServer Pages also became cornerstones for the J2EE platform Thesecomponent models have been widely-adopted as the basis for web applications, by themselves or as afront-end to Enterprise JavaBeans

Jon Kannegaard joined JavaSoft as vice president and general manager in late 1995 He was the singlemost important person involved in the delivery of Java technology in the years that followed J2EE inparticular would never have happened without his fight for the cause He got it He had faith Jon and I

recruited Mala Chandra to direct the enterprise work in mid-1996 I was very glad to have her on board;

I was doing all management and no engineering by that time Mala built an impressive organization veryquickly She utilized her wide respect in the industry to build support She provided a clear vision for aJ2EE platform She led us to success

Mala hired her former colleague Shel Finkelstein soon after her arrival Shel managed most of the J2EEarchitecture team and served as a core J2EE architect himself More importantly, he handled technicaldiplomacy with the partners Partnership turned out to be the quintessential element of the project:Without the long list of people and companies that committed to the J2EE effort and industry

consensus, the platform would not have developed the tremendous momentum it has today

By the beginning of 1998, Mala's engineering team numbered 60 people Two key additions were JeffJackson and Bill Shannon Bill became an essential member of the core architectural team, resolvingthe many technical issues in our weekly meetings We really needed his insight Jeff Jackson wanderedthe halls chanting the mantra "4, 6, 9, 1"—the months we had targeted in 1999 for the prealpha, alpha,beta, and final releases of J2EE We made those dates, and after the successful 12/99 release Jeff waspromoted to direct J2EE engineering

It is not practical to acknowledge here the dozens of people in J2EE engineering who worked beyondthe call of duty for the cause However, I must mention Sanjeev Krishnan, Carla Mott, Vivek Nagar, VellaRaman, and Anil Vijendran, whose contributions were truly outstanding You will find many othersacknowledged in the J2EE specifications and elsewhere

The excellent engineering management team is also due credit for the timeliness and quality of J2EE:Janet Breuer, Carla Carlson, Jim Driscoll, David Heisser, Jim Inscore, Tom Kincaid, Stans Kleijnen,

Achanta, and Gina Centoni managed J2EE marketing

However it should be said that the most important contributors were not Sun Microsystems employees.J2EE was an industry-wide effort Experts from dozens of partner companies successfully developedand reached consensus on J2EE APIs These APIs encompass a broad range of capabilities includingnaming and directory services, distributed transactions, OMG CORBA connectivity, asynchronousmessaging, security, web server development, enterprise application integration, EJB, and JDBC.Dave Rosenberg from Oracle and Ian Brackenbury from IBM had the tough job of bringing together thediverse viewpoints of their large companies to facilitate consensus on these APIs Rod Butters, MathieuDevin, Hal Hilderbrand, Larry Jacobs, Julie Basi, and Gary Hallmark from Oracle, Jack Boyce, EliasBayeh, Mike Connor, George Copeland, Paul Cotton, Don Ferguson, Tom Freund, Simon Nash, PeterNiblett, and Tony Storey from IBM, Scott Dietzen, Ed Cobb, Mark Carges, and Pete Homan from BEA,Johannes Klein from Compaq, Mary Leland from HP, Steve Holbrook and Art Navajjrez from Novell,Paul Butterworth and Sean Fitts from Forté, Vijay Anand, Yarden Malka, and Peter Yared from

NetDynamics, Marc San Soucie from GemStone, Richard Pledereder from Sybase, John Goodson fromMerant, Yeh-Heng Sheng from Informix, Larry Ciscon and Bernard Barcio from Modulus, Terry Olkinfrom Open Horizon, and Pete Ohler from Tibco were particularly helpful in bringing their expertise andtheir company viewpoints to the J2EE effort Many others are acknowledged in the J2EE specificationsfor their contributions to various APIs

The consensus-building process which began with JDBC was refined through these and other efforts,and eventually became the Java Community Process This process has proven very successful inachieving industry adoption of real standards while minimizing the "design by committee" that oftenplagues formal standards processes The Java Community Process avoids a "paper design" throughthe participation of engineers whose success depends on delivery of products that implement an API,and by demanding a reference implementation and compatibility test suite that give the standard

substance

The Java platform has come a long way from the first JavaOne conference in 1996 At that conference,

side Internet browsers At the third JavaOne in 1998, nearly 8,000 developers attended the presentationabout the enterprise Java platform Over half of them raised their hands when I asked who was writingserver-side Java code In early 2000, a dozen vendors have already announced server products

we introduced JDBC to an audience of developers who were using the Java platform primarily in client-expected to comply with the J2EE specification and compatibility test suite by year-end 100,000

enterprise developers have downloaded the J2EE reference implementation in just the few monthssince its December release We're delighted We hope that you too will find our work useful

Rick Cattell, Distinguished Engineer, Sun Microsystems

Cupertino, California, March 15, 2000

Bill Shannon is a Distinguished Engineer at Sun Microsystems, where he is one of the architects of the

J2EE He previously worked on the JavaMail API, the Hot-Java Views product, the Common DesktopEnvironment, the Solaris operating system, and all versions of SunOS

Mark Hapner is Lead Architect for the Java 2 Platform, Enterprise Edition He participated in the

development of the JDBC API, wrote the Java Message Service specification, and co-authored theEnterprise JavaBeans specification

Vlada Matena is a Distinguished Engineer with the Java Software division of Sun Microsystems Inc.,

where he works on the J2EE architecture team He is the Chief Architect of the Enterprise JavaBeansspecification, and an architect of the JTS and JTA specifications

James Davidson is a Staff Engineer at Sun Microsystems, working on web server–related

technologies Before joining Sun, James was involved in building some of the very first e-commercesites on the World Wide Web