100% found this document useful (3 votes)
28 views

Sun Certified Enterprise Architect for Java EE Study Guide 2nd Edition Mark Cade 2024 scribd download

Guide

Uploaded by

rokhimamoni32
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (3 votes)
28 views

Sun Certified Enterprise Architect for Java EE Study Guide 2nd Edition Mark Cade 2024 scribd download

Guide

Uploaded by

rokhimamoni32
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 36

Download the full version of the ebook at

https://ebookgate.com

Sun Certified Enterprise Architect for Java


EE Study Guide 2nd Edition Mark Cade

https://ebookgate.com/product/sun-certified-
enterprise-architect-for-java-ee-study-guide-2nd-
edition-mark-cade/

Explore and download more ebook at https://ebookgate.com


Recommended digital products (PDF, EPUB, MOBI) that
you can download immediately if you are interested.

Sun Certified Enterprise Architecture for J2EE Technology


Study Guide Mark Cade

https://ebookgate.com/product/sun-certified-enterprise-architecture-
for-j2ee-technology-study-guide-mark-cade/

ebookgate.com

Sun Certified Programmer Developer for Java 2 Study Guide


Exam 310 035 310 027 1st Edition Kathy Sierra

https://ebookgate.com/product/sun-certified-programmer-developer-for-
java-2-study-guide-exam-310-035-310-027-1st-edition-kathy-sierra/

ebookgate.com

SCJA Sun Certified Java Associate Study Guide Exam CX 310


019 Certification Press 1st Edition Robert Liguori

https://ebookgate.com/product/scja-sun-certified-java-associate-study-
guide-exam-cx-310-019-certification-press-1st-edition-robert-liguori/

ebookgate.com

Java EE 7 Developer Handbook Develop professional


applications in Java EE 7 with this essential reference
guide 7th Edition Peter A. Pilgrim
https://ebookgate.com/product/java-ee-7-developer-handbook-develop-
professional-applications-in-java-ee-7-with-this-essential-reference-
guide-7th-edition-peter-a-pilgrim/
ebookgate.com
Sun Certified Web Component Developer Study Guide Exams
310 081 310 082 Oracle Press 1st Edition David Bridgewater

https://ebookgate.com/product/sun-certified-web-component-developer-
study-guide-exams-310-081-310-082-oracle-press-1st-edition-david-
bridgewater/
ebookgate.com

CISSP Certified Information Systems Security Professional


Study Guide 2nd Edition Ed Tittle

https://ebookgate.com/product/cissp-certified-information-systems-
security-professional-study-guide-2nd-edition-ed-tittle/

ebookgate.com

OCA Oracle Certified Associate Java SE 8 Programmer I


Study Guide Exam 1Z0 808 1st Edition Jeanne Boyarsky

https://ebookgate.com/product/oca-oracle-certified-associate-java-
se-8-programmer-i-study-guide-exam-1z0-808-1st-edition-jeanne-
boyarsky/
ebookgate.com

TOGAF 9 Certified Study Guide First Edition, Impression


Edition Rachel Harrison

https://ebookgate.com/product/togaf-9-certified-study-guide-first-
edition-impression-edition-rachel-harrison/

ebookgate.com

CBAP CCBA Certified Business Analysis Study Guide 1st


Edition Susan Weese

https://ebookgate.com/product/cbap-ccba-certified-business-analysis-
study-guide-1st-edition-susan-weese/

ebookgate.com
Sun Certified Enterprise Architect
for Java™ EE Study Guide
Second Edition

Mark Cade and Humphrey Sheil

Upper Saddle River, NJ • Boston • Indianapolis • San Francisco


New York • Toronto • Montreal • London • Munich • Paris • Madrid
Cape Town • Sydney • Tokyo • Singapore • Mexico City
Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks.
Where those designations appear in this book, and the publisher was aware of a trademark claim, the designations
have been printed with initial capital letters or in all capitals.
Sun Microsystems, Inc. has intellectual property rights relating to implementations of the technology described in
this publication. In particular, and without limitation, these intellectual property rights may include one or more U.S.
patents, foreign patents, or pending applications.
Sun, Sun Microsystems, the Sun logo, J2ME, J2EE, Java Card, and all Sun and Java based trademarks and logos are
trademarks or registered trademarks of Sun Microsystems, Inc., in the United States and other countries. UNIX is a
registered trademark in the United States and other countries, exclusively licensed through X/Open Company, Ltd.
This publication is provided “as is” without warranty of any kind, either express or implied, including, but not limited
to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This publication
could include technical inaccuracies or typographical errors. Changes are periodically added to the information
herein; these changes will be incorporated in new editions of the publication. Sun Microsystems, Inc. may make
improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time.
The authors and publisher have taken care in the preparation of this book, but make no expressed or implied
warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or
consequential damages in connection with or arising out of the use of the information or programs contained herein.
The publisher offers excellent discounts on this book when ordered in quantity for bulk purchases or special sales,
which may include electronic versions and/or custom covers and content particular to your business, training goals,
marketing focus, and branding interests. For more information, please contact:
U.S. Corporate and Government Sales
(800) 382-3419
[email protected]
For sales outside the United States, please contact:
International Sales
[email protected]
Visit us on the Web: informit.com/ph
Library of Congress Cataloging-in-Publication Data:
Cade, Mark.
Sun Certified Enterprise Architect for Java EE study guide / Mark Cade, Humphrey Sheil. — 2nd ed.
p. cm.
Previous ed.: Sun Certified Enterprise Architect for J2EE technology study guide, 2002.
ISBN 978-0-13-148203-6 (pbk. : alk. paper) 1. Electronic data processing personnel—Certification. 2. Java
(Computer program language)—Examinations—Study guides. I. Sheil, Humphrey. II. Cade, Mark. Sun Certified
Enterprise Architect for J2EE technology study guide. III. Title.
QA76.3.C23 2010
005.13’3—dc22
2009052010
Copyright © 2010 Sun Microsystems, Inc.
All rights reserved. Printed in the United States of America. This publication is protected by copyright, and
permission must be obtained from the publisher prior to any prohibited reproduction, storage in a retrieval system,
or transmission in any form or by any means, electronic, mechanical, photocopying, recording, or likewise. For
information regarding permissions, write to:
Pearson Education, Inc
Rights and Contracts Department
501 Boylston Street, Suite 900
Boston, MA 02116
Fax (617) 671 3447
ISBN-13: 978-0-13-148203-6
ISBN-10: 0-13-148203-3
Text printed in the United States on recycled paper at RR Donnelley in Crawfordsville, Indiana
First printing February 2010
I dedicate this book to my lovely wife Lara for putting up with all the long hours.
Your support, compassion, and love drove me to finish this book. I look forward to
a wonderful vacation to make up for the time spent on this book.
—Mark Cade

I wish the reader of this book the very best toward passing the SCEA exam,
and in the process, becoming a better architect. Better architects create better
designs and code—and that’s what we all strive to do.
—Humphrey Sheil
This page intentionally left blank
Contents

Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . xv
About the Authors . . . . . . . . . . . . . . . . . . . . . . . xvii

Chapter 1 What Is Architecture? . . . . . . . . . . . . . . . . . . . . . . 1


Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Prerequisite Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Understanding Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Role of the Architect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
More Detail on the Exam Itself . . . . . . . . . . . . . . . . . . . . . . . . . 6
Part I: Multiple Choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Part II: Solving the Business Problem . . . . . . . . . . . . . . . . . . . 8
Part III: Defending Your Solution . . . . . . . . . . . . . . . . . . . . . . . 9
Preparing for the Exam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Preparing for Part I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Preparing for Part II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Preparing for Part III . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Essential Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Review Your Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2 Architecture Decomposition . . . . . . . . . . . . . . . . 13


Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Prerequisite Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Decomposition Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Layering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Exposure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
viii Contents

Generality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Coupling and Cohesion . . . . . . . . . . . . . . . . . . . . . . . . 16
Volatility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Planning and Tracking . . . . . . . . . . . . . . . . . . . . . . . . . 17
Work Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Tiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Business . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Virtual Platform (Component APIs) . . . . . . . . . . . . . . . . 19
Application Infrastructure (Containers) . . . . . . . . . . . . . 19
Enterprise Services (OS and Virtualization) . . . . . . . . . . 19
Compute and Storage . . . . . . . . . . . . . . . . . . . . . . . . . 19
Networking Infrastructure . . . . . . . . . . . . . . . . . . . . . . 20
Service-Level Requirements . . . . . . . . . . . . . . . . . . . . . . . . 20
Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Extensibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Maintainability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Manageability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Impact of Dimensions on Service-Level Requirements . . . . . . 23
Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Modularity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Workload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Heterogeneity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Common Practices for Improving Service-Level
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Introducing Redundancy to the System
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Improving Performance . . . . . . . . . . . . . . . . . . . . . . . . 27
Contents ix

Improving Availability . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Improving Extensibility . . . . . . . . . . . . . . . . . . . . . . . . . 29
Improving Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Tiers in Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Two-Tier Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Disadvantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Three- and Multi-Tier Systems . . . . . . . . . . . . . . . . . . . . . . . 31
Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Disadvantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Essential Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Review Your Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 3 Web Tier Technologies . . . . . . . . . . . . . . . . . . . . . 35


Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Prerequisite Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Model View Controller (MVC) . . . . . . . . . . . . . . . . . . . . . . . . 36
Web Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Servlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Listeners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
JavaServer Pages (JSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Java Standard Tag Library (JSTL) . . . . . . . . . . . . . . . . . . . . . . 40
Unified Expression Language (EL) . . . . . . . . . . . . . . . . . . . . . 40
Managing Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
JavaServer Faces (JSF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Templating Frameworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Web Frameworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
JSPs and Servlets—Standard Uses . . . . . . . . . . . . . . . . . . . 42
JSF—Standard Uses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Web-Centric Implementations . . . . . . . . . . . . . . . . . . . . . . . . 43
EJB-Centric Implementations . . . . . . . . . . . . . . . . . . . . . . . . 44
Rationale for Choosing Between EJB-Centric and
Web-Centric Implementations . . . . . . . . . . . . . . . . . . . . . . 45
The Future of Client-Server Communication . . . . . . . . . . . . . . 46
Essential Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Review Your Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
x Contents

Chapter 4 Business Tier Technologies . . . . . . . . . . . . . . . . . 51


Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Prerequisite Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Enterprise Java Bean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Session Bean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Stateless Session Bean . . . . . . . . . . . . . . . . . . . . . . . 54
Stateful Session Bean . . . . . . . . . . . . . . . . . . . . . . . . . 55
Entity Beans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
CMP Entity Bean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
BMP Entity Bean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Entity Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Persistence Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Message-Driven Bean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
EJB Advantages and Disadvantages . . . . . . . . . . . . . . . . . . . 59
Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Contrasting Persistence Strategies . . . . . . . . . . . . . . . . . . . . 60
Ease of Development . . . . . . . . . . . . . . . . . . . . . . . . . 60
Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Extensibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
EJB and Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
EJBs as Web Service End Points . . . . . . . . . . . . . . . . . . 61
EJBs Consuming Web Services . . . . . . . . . . . . . . . . . . 61
Advantages and Disadvantages . . . . . . . . . . . . . . . . . . 62
EJB 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Ease of Development . . . . . . . . . . . . . . . . . . . . . . . . . 63
Container in EJB 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
JPA in EJB 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Essential Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Review Your Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 5 Integration and Messaging. . . . . . . . . . . . . . . . . . 69


Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Prerequisite Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
SOAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
WSDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Contents xi

JAX-RPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
JAX-WS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
JAXB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
JAXR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
JMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
JCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Java to Java Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Java Messaging Service (JMS) . . . . . . . . . . . . . . . . . . . 76
Java to Non-Java Integration . . . . . . . . . . . . . . . . . . . . . . . . . 76
Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Java Connector Architecture (JCA) . . . . . . . . . . . . . . . . . 77
Essential Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Review Your Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Chapter 6 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Prerequisite Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
JRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
JAAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Credential . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Principal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Client-Side Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Server-Side Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
EJB Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Web Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Putting the EJB Container and Web
Container Together . . . . . . . . . . . . . . . . . . . . . . . . . 89
Web Service Security . . . . . . . . . . . . . . . . . . . . . . . . . . 90
How Security Behavior Is Defined . . . . . . . . . . . . . . . . . . . . . 91
Declarative Security . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Programmatic Security . . . . . . . . . . . . . . . . . . . . . . . . 92
Commonly Encountered Security Threats . . . . . . . . . . . . . . . 93
Defining a Security Model . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Essential Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Review Your Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
xii Contents

Chapter 7 Applying Patterns . . . . . . . . . . . . . . . . . . . . . . . . . 99


Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Prerequisite Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Creational Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Abstract Factory Pattern . . . . . . . . . . . . . . . . . . . . . . 101
Builder Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Factory Method Pattern . . . . . . . . . . . . . . . . . . . . . . . 104
Prototype Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Singleton Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Structural Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Adapter Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Bridge Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Composite Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Decorator Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Façade Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Flyweight Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Proxy Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Behavioral Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Chain of Responsibility Pattern . . . . . . . . . . . . . . . . . 115
Command Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Interpreter Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Iterator Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Mediator Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Memento Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Observer Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
State Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Strategy Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Template Method Pattern . . . . . . . . . . . . . . . . . . . . . 124
Visitor Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Core Java EE Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Presentation Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Intercepting Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Context Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Front Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Application Controller . . . . . . . . . . . . . . . . . . . . . . . . 129
View Helper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Contents xiii

Composite View . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130


Dispatcher View . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Service to Worker . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Business Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Business Delegate . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Service Locator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Session Façade . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Application Service . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Business Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Composite Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Transfer Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Transfer Object Assembler . . . . . . . . . . . . . . . . . . . . . 138
Value List Handler . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Integration Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Data Access Object . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Service Activator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Domain Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Web Service Broker . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Essential Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Review Your Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Chapter 8 Documenting an Architecture. . . . . . . . . . . . . . . 149


Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Prerequisite Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Building Blocks of UML . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Structural Elements . . . . . . . . . . . . . . . . . . . . . . . . . 151
Behavioral Elements . . . . . . . . . . . . . . . . . . . . . . . . . 152
Grouping Element . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Annotational Elements . . . . . . . . . . . . . . . . . . . . . . . 153
Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Common Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Adornments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Common Divisions . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Extensibility Mechanisms . . . . . . . . . . . . . . . . . . . . . 156
UML Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
xiv Contents

Structure Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157


Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Component Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 157
Deployment Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 159
Package Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Behavior Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Activity Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Statechart Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Use-Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Interaction Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Essential Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Review Your Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Chapter 9 Tackling Parts II and III . . . . . . . . . . . . . . . . . . . . 167


Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Prerequisite Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Worked Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Component Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Deployment Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Sequence Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Comments on Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Identified Risks and Mitigations . . . . . . . . . . . . . . . . . . . . . 178
Part III—Defending Your Architecture . . . . . . . . . . . . . . . . . . . 179
Essential Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Acknowledgments

Mark wishes to thank all of his past colleagues who have been great
sounding boards in developing material for creating architectures.

Humphrey would like to thank the Java EE community, inside and out-
side Sun Microsystems, for building and growing the JEE platform to
where it is today. A rich, vibrant programming platform needs good
design leadership to take it forward, and that is what the SCEA certifica-
tion, and this book, strives to engender.

The authors would also like to thank all those who provided great feed-
back to help improve this book, including Ken Saks and Chris Herron.
This page intentionally left blank
About the Authors

Mark Cade is a lead developer and assessor for the Sun Certified Enterprise
Architect for Java EE exam. He has more than 20 years of experience as a software
engineer and has extensive experience creating architectures for Java EE solutions
for Fortune 500 companies. He worked at the Sun Microsystems Java Center as a
Senior Java Architect until 2006. He is currently employed at BigFix.

Humphrey Sheil is a lead developer and assessor for the Sun Certified Enterprise
Architect for Java EE exam. With a background specializing in enterprise architec-
ture and integration in the United States and Europe, he holds a M.Sc. and B.Sc. in
Computer Science from University College Dublin. He is currently the CTO at
Comtec Group.
This page intentionally left blank
C H A P T E R 1

What Is Architecture?

Introduction

The Sun Certified Enterprise Architect exam is comprised of three


parts: knowledge-based multiple choice, assignment, and questions that
each requires a short essay answer. You must pass all three parts in order
to complete your certification.
Each subsequent chapter in this book will follow the same basic
structure. The chapter starts with a listing of the exam objectives that are
described in the chapter, followed by a “Prerequisite Review” section,
which identifies any assumed knowledge for the chapter and provides
other reading material to acquire the assumed knowledge. A “Discus-
sion” section, which describes the topics in the chapter with a focus on
the exam objectives, is next. This is followed by “Essential Points,” which
is a summary of the key ideas in the chapter. Finally, the “Review Your
Progress” section focuses on questions that might appear on the exam.
This first chapter will lay the groundwork for an understanding of
how the exam developers define architecture and some common termi-
nology. Having this understanding will help you in each of the subse-
quent chapters.

Prerequisite Review

This book assumes a certain level of knowledge for the readers. If you do
not have the prerequisite knowledge, you must gain this knowledge else-
where before proceeding with this book. Each chapter will have a list of
prerequisite knowledge for the objectives covered in that chapter. This
set of prerequisites covers the entire book:

1
2 Chapter 1 What Is Architecture?

■ You understand object-oriented concepts, such as encapsulation,


inheritance, polymorphism, and interfaces.
■ You have programmed in an objected-oriented language, prefer-
ably the Java programming language.
■ You have designed object-oriented programs and systems.
■ You are using this book to prepare for the Sun Certified Enter-
prise Architect (SCEA) for Java Enterprise Edition Technology
exam.

Becoming a full-fledged system architect requires many years of real-


world experience creating architectures and designing systems. This
book is not a substitute for that experience, but a study guide to assist
you on your path to become a Sun Certified Enterprise Architect for
Java Enterprise Edition (JEE) technology. As a study guide, it will make
assumptions about knowledge you should have and only cover the key
details for the exam.

Discussion

The best starting point for this book is to make sure that you are on the
same page as the exam developers. Having this common vocabulary will
reduce confusion in the later chapters. A clear and concise definition of
architecture is imperative to your success on this exam. Once you under-
stand the definition, you must understand your role in creating architec-
ture. You must realize what your tasks are. Finally, you must understand
the purpose of creating architecture. You create architecture to support
the service-level requirements of a system. Without service-level
requirements, your systems cannot meet customer demand for availabil-
ity, reliability, and scalability. These service-level requirements keep a
company from having a “CNN” moment, which occurs when the failure
of your computer systems makes headline news on CNN.

Understanding Architecture
According to the Rational Unified Process:

Software architecture encompasses the significant decisions


about the organization of a software system. The selection of the
Discussion 3

structural elements and their interfaces by which the system is


composed together with their behavior as specified in the collab-
oration among those elements. The composition of the struc-
tural and behavioral elements into progressively larger
subsystems, the architectural style that guides this organization,
these elements, and their interfaces, their collaborations, and
their composition. Software architecture is concerned not only
with structure and behavior but also with usage, functionality,
performance, resilience, reuse, comprehensibility, economic
and technology constraints and trade-offs, and aesthetic issues.1

That is a lengthy definition, so let’s look at a simpler definition provided


by the SunTone Architecture Methodology:

Architecture is a set of structuring principles that enables a sys-


tem to be comprised of a set of simpler systems each with its
own local context that is independent of but not inconsistent
with the context of the larger system as a whole.2

Both definitions focus on system structure. You create architecture to


describe the structure of the system to be built and how that structure
supports the business and service-level requirements. You can define the
structure of a system as the mechanisms that the system employs to solve
the common problems of the system. A mechanism is a capability that
supports the business requirements in a consistent and uniform manner.
For example, persistence is a mechanism that should be used consis-
tently throughout the system. This means that, any time the system uses
persistence, it is handled in the same manner. By defining persistence as
an architectural mechanism, you provide a default method of addressing
persistence that all designers should follow and implement consistently.
The architectural mechanisms—such as persistence, distribution, com-
munication, transaction management, and security—are the infrastruc-
ture on which you build the system and must be defined in your
architecture.

1 Philippe Kruchten, The Rational Unified Process: An Introduction, Third Edition


(Upper Saddle River, NJ: Addison-Wesley Professional, 2003).
2 Sun Microsystems, Inc.
Another random document with
no related content on Scribd:
*** END OF THE PROJECT GUTENBERG EBOOK PARENT ÚR ***

Updated editions will replace the previous one—the old editions will
be renamed.

Creating the works from print editions not protected by U.S.


copyright law means that no one owns a United States copyright in
these works, so the Foundation (and you!) can copy and distribute it
in the United States without permission and without paying copyright
royalties. Special rules, set forth in the General Terms of Use part of
this license, apply to copying and distributing Project Gutenberg™
electronic works to protect the PROJECT GUTENBERG™ concept
and trademark. Project Gutenberg is a registered trademark, and
may not be used if you charge for an eBook, except by following the
terms of the trademark license, including paying royalties for use of
the Project Gutenberg trademark. If you do not charge anything for
copies of this eBook, complying with the trademark license is very
easy. You may use this eBook for nearly any purpose such as
creation of derivative works, reports, performances and research.
Project Gutenberg eBooks may be modified and printed and given
away—you may do practically ANYTHING in the United States with
eBooks not protected by U.S. copyright law. Redistribution is subject
to the trademark license, especially commercial redistribution.

START: FULL LICENSE


THE FULL PROJECT GUTENBERG LICENSE
PLEASE READ THIS BEFORE YOU DISTRIBUTE OR USE THIS WORK

To protect the Project Gutenberg™ mission of promoting the free


distribution of electronic works, by using or distributing this work (or
any other work associated in any way with the phrase “Project
Gutenberg”), you agree to comply with all the terms of the Full
Project Gutenberg™ License available with this file or online at
www.gutenberg.org/license.

Section 1. General Terms of Use and


Redistributing Project Gutenberg™
electronic works
1.A. By reading or using any part of this Project Gutenberg™
electronic work, you indicate that you have read, understand, agree
to and accept all the terms of this license and intellectual property
(trademark/copyright) agreement. If you do not agree to abide by all
the terms of this agreement, you must cease using and return or
destroy all copies of Project Gutenberg™ electronic works in your
possession. If you paid a fee for obtaining a copy of or access to a
Project Gutenberg™ electronic work and you do not agree to be
bound by the terms of this agreement, you may obtain a refund from
the person or entity to whom you paid the fee as set forth in
paragraph 1.E.8.

1.B. “Project Gutenberg” is a registered trademark. It may only be


used on or associated in any way with an electronic work by people
who agree to be bound by the terms of this agreement. There are a
few things that you can do with most Project Gutenberg™ electronic
works even without complying with the full terms of this agreement.
See paragraph 1.C below. There are a lot of things you can do with
Project Gutenberg™ electronic works if you follow the terms of this
agreement and help preserve free future access to Project
Gutenberg™ electronic works. See paragraph 1.E below.
1.C. The Project Gutenberg Literary Archive Foundation (“the
Foundation” or PGLAF), owns a compilation copyright in the
collection of Project Gutenberg™ electronic works. Nearly all the
individual works in the collection are in the public domain in the
United States. If an individual work is unprotected by copyright law in
the United States and you are located in the United States, we do
not claim a right to prevent you from copying, distributing,
performing, displaying or creating derivative works based on the
work as long as all references to Project Gutenberg are removed. Of
course, we hope that you will support the Project Gutenberg™
mission of promoting free access to electronic works by freely
sharing Project Gutenberg™ works in compliance with the terms of
this agreement for keeping the Project Gutenberg™ name
associated with the work. You can easily comply with the terms of
this agreement by keeping this work in the same format with its
attached full Project Gutenberg™ License when you share it without
charge with others.

1.D. The copyright laws of the place where you are located also
govern what you can do with this work. Copyright laws in most
countries are in a constant state of change. If you are outside the
United States, check the laws of your country in addition to the terms
of this agreement before downloading, copying, displaying,
performing, distributing or creating derivative works based on this
work or any other Project Gutenberg™ work. The Foundation makes
no representations concerning the copyright status of any work in
any country other than the United States.

1.E. Unless you have removed all references to Project Gutenberg:

1.E.1. The following sentence, with active links to, or other


immediate access to, the full Project Gutenberg™ License must
appear prominently whenever any copy of a Project Gutenberg™
work (any work on which the phrase “Project Gutenberg” appears, or
with which the phrase “Project Gutenberg” is associated) is
accessed, displayed, performed, viewed, copied or distributed:
This eBook is for the use of anyone anywhere in the United
States and most other parts of the world at no cost and with
almost no restrictions whatsoever. You may copy it, give it away
or re-use it under the terms of the Project Gutenberg License
included with this eBook or online at www.gutenberg.org. If you
are not located in the United States, you will have to check the
laws of the country where you are located before using this
eBook.

1.E.2. If an individual Project Gutenberg™ electronic work is derived


from texts not protected by U.S. copyright law (does not contain a
notice indicating that it is posted with permission of the copyright
holder), the work can be copied and distributed to anyone in the
United States without paying any fees or charges. If you are
redistributing or providing access to a work with the phrase “Project
Gutenberg” associated with or appearing on the work, you must
comply either with the requirements of paragraphs 1.E.1 through
1.E.7 or obtain permission for the use of the work and the Project
Gutenberg™ trademark as set forth in paragraphs 1.E.8 or 1.E.9.

1.E.3. If an individual Project Gutenberg™ electronic work is posted


with the permission of the copyright holder, your use and distribution
must comply with both paragraphs 1.E.1 through 1.E.7 and any
additional terms imposed by the copyright holder. Additional terms
will be linked to the Project Gutenberg™ License for all works posted
with the permission of the copyright holder found at the beginning of
this work.

1.E.4. Do not unlink or detach or remove the full Project


Gutenberg™ License terms from this work, or any files containing a
part of this work or any other work associated with Project
Gutenberg™.

1.E.5. Do not copy, display, perform, distribute or redistribute this


electronic work, or any part of this electronic work, without
prominently displaying the sentence set forth in paragraph 1.E.1 with
active links or immediate access to the full terms of the Project
Gutenberg™ License.
1.E.6. You may convert to and distribute this work in any binary,
compressed, marked up, nonproprietary or proprietary form,
including any word processing or hypertext form. However, if you
provide access to or distribute copies of a Project Gutenberg™ work
in a format other than “Plain Vanilla ASCII” or other format used in
the official version posted on the official Project Gutenberg™ website
(www.gutenberg.org), you must, at no additional cost, fee or expense
to the user, provide a copy, a means of exporting a copy, or a means
of obtaining a copy upon request, of the work in its original “Plain
Vanilla ASCII” or other form. Any alternate format must include the
full Project Gutenberg™ License as specified in paragraph 1.E.1.

1.E.7. Do not charge a fee for access to, viewing, displaying,


performing, copying or distributing any Project Gutenberg™ works
unless you comply with paragraph 1.E.8 or 1.E.9.

1.E.8. You may charge a reasonable fee for copies of or providing


access to or distributing Project Gutenberg™ electronic works
provided that:

• You pay a royalty fee of 20% of the gross profits you derive from
the use of Project Gutenberg™ works calculated using the
method you already use to calculate your applicable taxes. The
fee is owed to the owner of the Project Gutenberg™ trademark,
but he has agreed to donate royalties under this paragraph to
the Project Gutenberg Literary Archive Foundation. Royalty
payments must be paid within 60 days following each date on
which you prepare (or are legally required to prepare) your
periodic tax returns. Royalty payments should be clearly marked
as such and sent to the Project Gutenberg Literary Archive
Foundation at the address specified in Section 4, “Information
about donations to the Project Gutenberg Literary Archive
Foundation.”

• You provide a full refund of any money paid by a user who


notifies you in writing (or by e-mail) within 30 days of receipt that
s/he does not agree to the terms of the full Project Gutenberg™
License. You must require such a user to return or destroy all
copies of the works possessed in a physical medium and
discontinue all use of and all access to other copies of Project
Gutenberg™ works.

• You provide, in accordance with paragraph 1.F.3, a full refund of


any money paid for a work or a replacement copy, if a defect in
the electronic work is discovered and reported to you within 90
days of receipt of the work.

• You comply with all other terms of this agreement for free
distribution of Project Gutenberg™ works.

1.E.9. If you wish to charge a fee or distribute a Project Gutenberg™


electronic work or group of works on different terms than are set
forth in this agreement, you must obtain permission in writing from
the Project Gutenberg Literary Archive Foundation, the manager of
the Project Gutenberg™ trademark. Contact the Foundation as set
forth in Section 3 below.

1.F.

1.F.1. Project Gutenberg volunteers and employees expend


considerable effort to identify, do copyright research on, transcribe
and proofread works not protected by U.S. copyright law in creating
the Project Gutenberg™ collection. Despite these efforts, Project
Gutenberg™ electronic works, and the medium on which they may
be stored, may contain “Defects,” such as, but not limited to,
incomplete, inaccurate or corrupt data, transcription errors, a
copyright or other intellectual property infringement, a defective or
damaged disk or other medium, a computer virus, or computer
codes that damage or cannot be read by your equipment.

1.F.2. LIMITED WARRANTY, DISCLAIMER OF DAMAGES - Except


for the “Right of Replacement or Refund” described in paragraph
1.F.3, the Project Gutenberg Literary Archive Foundation, the owner
of the Project Gutenberg™ trademark, and any other party
distributing a Project Gutenberg™ electronic work under this
agreement, disclaim all liability to you for damages, costs and
expenses, including legal fees. YOU AGREE THAT YOU HAVE NO
REMEDIES FOR NEGLIGENCE, STRICT LIABILITY, BREACH OF
WARRANTY OR BREACH OF CONTRACT EXCEPT THOSE
PROVIDED IN PARAGRAPH 1.F.3. YOU AGREE THAT THE
FOUNDATION, THE TRADEMARK OWNER, AND ANY
DISTRIBUTOR UNDER THIS AGREEMENT WILL NOT BE LIABLE
TO YOU FOR ACTUAL, DIRECT, INDIRECT, CONSEQUENTIAL,
PUNITIVE OR INCIDENTAL DAMAGES EVEN IF YOU GIVE
NOTICE OF THE POSSIBILITY OF SUCH DAMAGE.

1.F.3. LIMITED RIGHT OF REPLACEMENT OR REFUND - If you


discover a defect in this electronic work within 90 days of receiving it,
you can receive a refund of the money (if any) you paid for it by
sending a written explanation to the person you received the work
from. If you received the work on a physical medium, you must
return the medium with your written explanation. The person or entity
that provided you with the defective work may elect to provide a
replacement copy in lieu of a refund. If you received the work
electronically, the person or entity providing it to you may choose to
give you a second opportunity to receive the work electronically in
lieu of a refund. If the second copy is also defective, you may
demand a refund in writing without further opportunities to fix the
problem.

1.F.4. Except for the limited right of replacement or refund set forth in
paragraph 1.F.3, this work is provided to you ‘AS-IS’, WITH NO
OTHER WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR ANY PURPOSE.

1.F.5. Some states do not allow disclaimers of certain implied


warranties or the exclusion or limitation of certain types of damages.
If any disclaimer or limitation set forth in this agreement violates the
law of the state applicable to this agreement, the agreement shall be
interpreted to make the maximum disclaimer or limitation permitted
by the applicable state law. The invalidity or unenforceability of any
provision of this agreement shall not void the remaining provisions.
1.F.6. INDEMNITY - You agree to indemnify and hold the
Foundation, the trademark owner, any agent or employee of the
Foundation, anyone providing copies of Project Gutenberg™
electronic works in accordance with this agreement, and any
volunteers associated with the production, promotion and distribution
of Project Gutenberg™ electronic works, harmless from all liability,
costs and expenses, including legal fees, that arise directly or
indirectly from any of the following which you do or cause to occur:
(a) distribution of this or any Project Gutenberg™ work, (b)
alteration, modification, or additions or deletions to any Project
Gutenberg™ work, and (c) any Defect you cause.

Section 2. Information about the Mission of


Project Gutenberg™
Project Gutenberg™ is synonymous with the free distribution of
electronic works in formats readable by the widest variety of
computers including obsolete, old, middle-aged and new computers.
It exists because of the efforts of hundreds of volunteers and
donations from people in all walks of life.

Volunteers and financial support to provide volunteers with the


assistance they need are critical to reaching Project Gutenberg™’s
goals and ensuring that the Project Gutenberg™ collection will
remain freely available for generations to come. In 2001, the Project
Gutenberg Literary Archive Foundation was created to provide a
secure and permanent future for Project Gutenberg™ and future
generations. To learn more about the Project Gutenberg Literary
Archive Foundation and how your efforts and donations can help,
see Sections 3 and 4 and the Foundation information page at
www.gutenberg.org.

Section 3. Information about the Project


Gutenberg Literary Archive Foundation
The Project Gutenberg Literary Archive Foundation is a non-profit
501(c)(3) educational corporation organized under the laws of the
state of Mississippi and granted tax exempt status by the Internal
Revenue Service. The Foundation’s EIN or federal tax identification
number is 64-6221541. Contributions to the Project Gutenberg
Literary Archive Foundation are tax deductible to the full extent
permitted by U.S. federal laws and your state’s laws.

The Foundation’s business office is located at 809 North 1500 West,


Salt Lake City, UT 84116, (801) 596-1887. Email contact links and up
to date contact information can be found at the Foundation’s website
and official page at www.gutenberg.org/contact

Section 4. Information about Donations to


the Project Gutenberg Literary Archive
Foundation
Project Gutenberg™ depends upon and cannot survive without
widespread public support and donations to carry out its mission of
increasing the number of public domain and licensed works that can
be freely distributed in machine-readable form accessible by the
widest array of equipment including outdated equipment. Many small
donations ($1 to $5,000) are particularly important to maintaining tax
exempt status with the IRS.

The Foundation is committed to complying with the laws regulating


charities and charitable donations in all 50 states of the United
States. Compliance requirements are not uniform and it takes a
considerable effort, much paperwork and many fees to meet and
keep up with these requirements. We do not solicit donations in
locations where we have not received written confirmation of
compliance. To SEND DONATIONS or determine the status of
compliance for any particular state visit www.gutenberg.org/donate.

While we cannot and do not solicit contributions from states where


we have not met the solicitation requirements, we know of no
prohibition against accepting unsolicited donations from donors in
such states who approach us with offers to donate.

International donations are gratefully accepted, but we cannot make


any statements concerning tax treatment of donations received from
outside the United States. U.S. laws alone swamp our small staff.

Please check the Project Gutenberg web pages for current donation
methods and addresses. Donations are accepted in a number of
other ways including checks, online payments and credit card
donations. To donate, please visit: www.gutenberg.org/donate.

Section 5. General Information About Project


Gutenberg™ electronic works
Professor Michael S. Hart was the originator of the Project
Gutenberg™ concept of a library of electronic works that could be
freely shared with anyone. For forty years, he produced and
distributed Project Gutenberg™ eBooks with only a loose network of
volunteer support.

Project Gutenberg™ eBooks are often created from several printed


editions, all of which are confirmed as not protected by copyright in
the U.S. unless a copyright notice is included. Thus, we do not
necessarily keep eBooks in compliance with any particular paper
edition.

Most people start at our website which has the main PG search
facility: www.gutenberg.org.

This website includes information about Project Gutenberg™,


including how to make donations to the Project Gutenberg Literary
Archive Foundation, how to help produce our new eBooks, and how
to subscribe to our email newsletter to hear about new eBooks.

You might also like