Java EE认证考试指南：Sun Certified Enterprise Architect

需积分: 9 31 浏览量更新于2024-07-31 收藏 2.27MB PDF 举报

"Sun Certified Enterprise Architect for J2EE Study Guide 是一本针对2010年发布的Java 2 EE认证考试的最新教材。本书由Mark Cade和Humphrey Sheil合著，旨在帮助读者准备并成功通过Sun Microsystems的Java企业架构师认证。" 《Sun Certified Enterprise Architect for Java™ EE Study Guide》第二版是Java 2 EE认证考试的必备参考资料，它覆盖了当时最新的考试大纲和技术内容。这本书不仅涵盖了Java企业级应用架构的基础知识，还深入讲解了设计和实现复杂企业级解决方案所需的技能。 Java 2 EE（Java Platform, Enterprise Edition）是Java技术在企业级开发中的核心框架，它提供了构建分布式、多层应用程序的组件和服务。这本教材将帮助读者理解和掌握J2EE平台的关键技术，包括Servlets、JSP（JavaServer Pages）、EJB（Enterprise JavaBeans）、JMS（Java Message Service）、JTA（Java Transaction API）以及XML和Web服务等。书中可能详细讨论了以下关键知识点： 1. **Servlets**：作为Java Web应用程序的核心，Servlets处理HTTP请求并生成响应，是构建动态网站和Web服务的基础。 2. **JSP**：JSP用于创建动态网页，结合了HTML和Java代码，使开发者可以更专注于页面展示逻辑，而将业务逻辑分离。 3. **EJB**：EJB是Java 2 EE的核心组件，提供了服务器端的组件模型，用于构建可伸缩、安全和事务性的企业级应用。EJB分为会话bean、实体bean和消息驱动bean三种类型。 4. **JMS**：Java消息服务允许应用程序之间异步通信，是企业级应用集成的重要部分。 5. **JTA**：Java事务API定义了管理事务的标准接口，确保在分布式环境中数据的一致性和完整性。 6. **XML和Web服务**：XML用于数据交换，而Web服务（如SOAP和RESTful）利用XML在不同系统间提供互操作性。 7. **设计模式和最佳实践**：书中可能会介绍在J2EE开发中广泛采用的设计模式，如工厂模式、单例模式和观察者模式，以及如何遵循最佳实践来提高代码质量和可维护性。 8. **企业架构原则**：书中可能涵盖了如何设计可扩展、灵活且可维护的系统，以及如何进行性能调优和故障排查。 9. **安全性**：Java 2 EE提供了强大的安全性框架，包括身份验证、授权和加密。书中的内容可能涵盖了如何实施这些安全措施。 10. **部署和测试**：有效的部署策略和自动化测试对于任何企业级应用的成功至关重要，书中可能会讨论这些问题。这本教材不仅适合准备认证考试的考生，也对任何希望深化Java 2 EE技术理解的开发人员具有极高的价值。通过深入学习和实践，读者可以提升自己在Java企业架构领域的专业能力，为解决复杂的企业级问题做好准备。

ptg

This page intentionally left blank

From the Library of Skyla Walker

ptg

Discussion

structural elements and their interfaces by which the system is

composed together with their behavior as speciﬁed 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.

That is a lengthy deﬁnition, so let’s look at a simpler deﬁnition 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.

Both deﬁnitions 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 deﬁne 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 deﬁning 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 deﬁned in your

architecture.

Philippe Kruchten, The Rational Uniﬁed Process: An Introduction, Third Edition

(Upper Saddle River, NJ: Addison-Wesley Professional, 2003).

Sun Microsystems, Inc.

From the Library of Skyla Walker

eBook from Wow! eBook dot com

ptg

Chapter 1 What Is Architecture?

What does it mean to create architecture? It means that you have

created a software infrastructure that addresses the service-level

requirements that have been identiﬁed for the system. For example, if

the system has a service-level requirement that states no user response

time will be greater than three seconds, the software infrastructure you

create must ensure that the system can meet this requirement. It also

means that you have given the designers an infrastructure that allows

them to design and code the system without worrying about compromis-

ing this service-level requirement. One of the real issues around archi-

tecture is: When does the creation of an architecture stop and the design

process begin? There is not a deﬁnitive answer for every system. This

issue of architecture and design can be summed up in terms of focus and

control. Architecture deﬁnes what is going to be built, and design out-

lines how you will build it. One or a few individuals who focus on the big

picture control the architectural process, and design is controlled by

many individuals who focus on the details of how to achieve the big pic-

ture. An architect creates architecture to a point where the design team

can use it to make the system achieve its overall goals. So, if you are cre-

ating an architecture for experienced designers, you would not produce

as much detailed documentation that you would need if you had a group

of less-experienced designers.

As you create an architecture to satisfy the business and service-level

requirements of a system, you usually don’t have unlimited funds to pur-

chase hardware, software and development resources, so you need to

make the system work within your predeﬁned limitations. For example,

how can you make the system scale to meet the demands of the Internet

age, when you have only a single computer to support your internal

employees? How do you create architecture without funds to buy soft-

ware products? These are examples of problems faced by architects

when they are creating system architecture. You will be presented with

many difﬁcult choices and make many trade-offs to solve these types of

problems when creating your architecture. As you make these trade-

offs, it is important that you document each decision made regarding the

architecture of the system, so developers understand why decisions were

made, and you should not receive questions from developers about

those trade-offs. If you make a decision to have an Oracle database

persist the objects in the system, you should document why you chose

Oracle over another database vendor. This allows others working on the

project or entering the project at a later time to understand why deci-

sions were made and prevents you from justifying your decision over and

From the Library of Skyla Walker

剩余211页未读，继续阅读

upbcswd

粉丝: 0
资源: 2

Java EE认证考试指南：Sun Certified Enterprise Architect

Sun Certified Enterprise Architect for J2EE™ Technology Study Guide

J2EE架构师的SCEA认证经验

JAVA高级开发与认证宝典：Sun Certified Enterprise Architect for Java EE

Java程序员哪些证书权威？

aws certified solutions architect - professional

GCP certified architect 试题解析

AWS SAA 题库

it有那些证书，有含金量

h3c certified network engineer for msa

主机方面的能力标签怎么写

最新资源