利用Java Web服务构建SOA：指南

4星 · 超过85%的资源需积分: 10 181 浏览量更新于2024-07-30 收藏 1.85MB PDF 举报

"《Prentice+SOA Using Java Web Services》是一本专门针对面向服务架构（SOA）和Java Web服务的深入指南。本书由Mark D. Hansen撰写，旨在帮助读者理解和应用SOA原则，特别是如何利用Java技术来构建和实现服务导向架构。SOA是一种软件设计和开发模式，它将企业应用程序分解为一组独立的服务，这些服务通过标准协议进行交互，从而提高系统的灵活性、可扩展性和集成性。在书中，作者探讨了以下几个关键知识点： 1. **Java Web服务基础**：讲解Java语言如何支持Web服务的创建、部署和消费，包括SOAP（简单对象访问协议）和RESTful（Representational State Transfer，资源表述状态转移）服务的设计与实现。 2. **服务架构设计**：涵盖了如何设计服务目录、服务接口规范、服务治理和安全性策略等内容，确保服务间的可靠通信和互操作性。 3. **服务生命周期管理**：涵盖了服务的创建、发布、调用、监控和维护等各个环节，以及如何利用企业服务总线（ESB）和容器来简化服务的集成和管理。 4. **服务组件和服务编排**：介绍如何使用微服务架构和容器化技术，如Docker，来构建和管理小型、独立的服务单元，并通过工具如Spring Boot或Apache Camel进行编排。 5. **云计算与SOA结合**：讨论了SOA在云环境中的应用，如使用AWS、Azure或Google Cloud Platform等云服务提供商提供的API和平台作为服务（PaaS）解决方案。 6. **案例研究和实战演练**：书中包含丰富的实践案例，通过实际项目演示如何将理论知识转化为实际的SOA项目，帮助读者掌握SOA实施的关键步骤。 7. **最佳实践和未来趋势**：最后，作者分享了SOA和Java Web服务领域的最佳实践，以及对行业发展趋势的见解，以助于读者紧跟技术潮流。值得注意的是，尽管这本书提供了丰富的信息，但它并不承诺对所有错误或遗漏负责，并且不承担因使用书中的信息或程序而产生的任何间接或附带损害的责任。此外，出版社还为批量购买或定制封面和内容的企业客户提供优惠，以满足特定的业务、培训目标和营销策略需求。《Prentice+SOA Using Java Web Services》是一本实用的工具书，适合IT专业人员、架构师和开发者提升在SOA领域的能力和知识。"

Foreword

Pat Helland, formerly of Microsoft, has a great acronym he likes to use

when talking about interoperability: HST, or “Hooking Stuff Together.”

(Actually, he uses an altogether different word there in the middle, but I’m

told this is a family book, so I paraphrased.) No matter how much you dress

it up in fancy words and complex ﬂowcharts, interoperability simply means

“Hooking Stuff Together”—something Web Services are all about.

Ever since the second computer came online, True Interoperability

remains the goal that still eludes us. IT environments are home to a wide array

of different technologies, all of which serve some useful purpose (or so I’m

told). Despite various vendors’ attempts to establish their tool of choice as the

sole/dominant tool for building (and porting) applications, the IT world has

only become more—not less—diverse. Numerous solutions have been posited

as “the answer” to the thorny problem of getting program “A” to be able to talk

to program “B,” regardless of what language, platform, operating system, or

hardware the two programs are written in or running on. None had proven to

be entirely successful, either requiring an “all-or-nothing” mentality, or offering

only solutions to handle the simplest situations and nothing more.

In 1998, Don Box and Dave Winer, along with a couple of guys from

Microsoft, IBM, and Lotus, sat down and wrote a short document

describing an idea for replicating a remote procedure call stack into an

XML message. The idea was simple: If all of the various distributed object

toolkits available at the time—DCOM, Java RMI, and CORBA being the

principal concerns—shared a common wire format, it would be a simple

matter to achieve the Holy Grail of enterprise IT programming: True

Interoperability.

In the beginning, SOAP held out the prospect of a simpler, better way

to Hook Stuff Together: XML, the lingua franca of data, passed over HTTP,

the Dark Horse candidate in the Distributed Object wars, with all the

semantics of the traditional distributed object programming model sur-

rounding it. It seemed an easy prospect; just slip the XML in where nobody

would see it, way down deep in the distributed object’s generated code.

What we didn’t realize at the time, unfortunately, was that this vision was all

xvi Foreword

too simplistic, and horribly naïve. It might work for environments that were

remarkably similar to one another (à la Java and .NET), but even there,

problems would arise, owing to differences XML simply couldn’t wash

away. Coupled with the fact that none of the so-called standards was, in fact,

a standard from any kind of legitimate standards body, and that vendors

were putting out “WS-Foo” speciﬁcations every time you turned around,

the intended simplicity of the solution was, in a word, absent. In fact, to put

it bluntly, for a long time, the whole Web Services story was more “mess”

than “message.”

In Chapter 1 of this book, Mark Hansen writes, “Web Services are not

easy.” Whatever happened to the “Simple” in “SOAP?”

Ironically, even as Web Services start to take on “dirty word” status,

alongside EJB and COBOL, the message is becoming increasingly clear,

and the chances of “getting it right” have never been higher. Distractions

such as the SOAP versus REST debate aside (which really isn’t a debate, as

anyone who’s really read the SOAP 1.2 spec and the REST dissertation can

tell), the various vendors and industry groups are ﬁnally coming to a point

where they can actually Hook Stuff Together in more meaningful ways than

just “I’ll pass you a string, which you’ll parse….”

As an instructor with DevelopMentor—where I taught Java, .NET, and

XML—I had the privilege of learning about SOAP, WSDL, and Web Ser-

vices from the very guys who were writing the specs, including Don Box and

Martin Gudgin, our representative to the W3C, who helped coauthor the

SOAP and Schema specs, among others. As an industry consultant focused

on interoperability between Java, .NET, and other platforms, I get a unique

ﬁrst-person view of real-world interoperability problems. And as an inde-

pendent speaker and mentor, I get to study the various interoperability tool-

kits and see how well they work.

Not everybody gets that chance, however, and unless you’re a real low-

level “plumbing” wonk like I am, and ﬁnd a twisted joy in reading through

the myriad WS-

*-related speciﬁcations, things like SOAP and WSDL

remain arcane, high-bar topics that seemingly nobody in his or her right

mind would attempt to learn, just to get your Java code to be able to talk to

other platforms. That’s okay; quite honestly, you shouldn’t have to. If you

have to absorb every level of detail in a given programming environment in

order to use it, well, something is wrong.

The JAX-WS and JAXB standards were created to help you avoid hav-

ing to know all those low-level, byzantine details of the Web Services

plumbing, unless and until you want to. Mark’s book will help you navigate

through the twisty parts of JAX-WS and JAXB because he’s been there. He

had to ﬁght his way through the mess to get to the message, and now he’s

剩余604页未读，继续阅读

jacklee_6297

粉丝: 13
资源: 29

利用Java Web服务构建SOA：指南

Prentice.Hall.SOA.Using.Java.Web.Services.May.2007

Prentice.Hall.Core.Java.Volume.II.Advanced.Features.10th.Edition.2017

[Prentice+Hall]+-+Thinking+in+C#

java 外文参考文献_java英文参考文献

关于Java的外文期刊参考文献

java编程思想 文献_JAVA编程思想英文参考文献和翻译

Cay S. Horstmann在其权威著作中是如何详细阐释面向对象开发三大核心概念：封装、继承和多态的？请结合《Cay S. Horstmann：C++、Java权威书籍作者与Prentice-Hall合作》一文内容，提供具体解答。

ε-closure（I）的程序实现课程实训参考文献

最新资源

java编程思想文献_JAVA编程思想英文参考文献和翻译