Java Web 服务快速入门：从基础到实践

PDF文件

下载需积分: 10 | 3.58MB | 更新于2024-07-27 | 67 浏览量 | 举报收藏

立即下载

Java Web服务概述 Java Web服务：Up and Running是O'Reilly出版的一本书籍，旨在帮助读者快速了解和掌握Java Web服务的相关知识。本书涵盖了Java Web服务的基本概念、架构、开发和部署等方面的内容。 Java Web服务的定义和特点 Java Web服务是一种基于XML的分布式应用程序交互机制，允许不同的应用程序之间进行交互和数据交换。Java Web服务的主要特点包括： * 基于XML的数据交换 * 使用SOAP（Simple Object Access Protocol）协议进行消息传递 * 支持多种编程语言和平台 * 允许跨平台和跨语言的应用程序集成 Java Web服务的架构 Java Web服务的架构主要包括三个部分： * 服务提供者（Service Provider）：提供Web服务的应用程序 * 服务注册中心（Service Registry）：存储和管理Web服务的信息 * 服务请求者（Service Requestor）：请求和使用Web服务的应用程序 Java Web服务的开发和部署 Java Web服务的开发和部署主要包括以下步骤： * 设计和实现Web服务接口 * 使用Java语言和相关框架实现Web服务 * 部署Web服务到应用服务器上 * 测试和调试Web服务 Java Web服务的优点和应用场景 Java Web服务的优点包括： * 跨平台和跨语言的应用程序集成 * 提高系统集成和可重用性 * 简化应用程序之间的交互和数据交换 Java Web服务的应用场景包括： * 企业应用系统集成 * 电子商务平台集成 * 移动应用程序开发 * 云计算和大数据处理相关资源和工具 O'Reilly提供了许多相关的资源和工具，包括： * Java和XML相关书籍 * Java Generics和Collections相关书籍 * Head First Java相关书籍 * Java in a Nutshell相关书籍 * Java Power Tools相关书籍 * Java Pocket Guide相关书籍 * Enterprise JavaBeans 3.0相关书籍 * Java Message Service相关书籍这些资源和工具可以帮助读者更好地理解和掌握Java Web服务的相关知识和技术。 Java Web服务：Up and Running是学习Java Web服务的优秀资源，涵盖了Java Web服务的基本概念、架构、开发和部署等方面的内容。

We appreciate, but do not require, attribution. An attribution usually includes the title,

author, publisher, and ISBN. For example: “Java Web Services: Up and Running, by

If you feel your use of code examples falls outside fair use or the permission given above,

feel free to contact us at [email protected].

Safari

Books Online

When you see a Safari

Books Online icon on the cover of your favorite

technology book, that means the book is available online through the

O’Reilly Network Safari Bookshelf.

Safari offers a solution that’s better than e-books. It’s a virtual library that lets you easily

search thousands of top tech books, cut and paste code samples, download chapters,

and find quick answers when you need the most accurate, current information. Try it

for free at http://safari.oreilly.com.

How to Contact Us

Please address comments and questions concerning this book to the publisher:

O’Reilly Media, Inc.

1005 Gravenstein Highway North

Sebastopol, CA 95472

800-998-9938 (in the United States or Canada)

707-829-0515 (international or local)

707-829-0104 (fax)

We have a web page for this book, where we list errata, examples, and any additional

information. You can access this page at:

http://www.oreilly.com/catalog/9780596521127/

To comment or ask technical questions about this book, send email to:

[email protected]

For more information about our books, conferences, Resource Centers, and the

O’Reilly Network, see our website at:

http://www.oreilly.com/

xiv | Preface

Download at Boykma.Com

CHAPTER 1

Java Web Services Quickstart

What Are Web Services?

Although the term web service has various, imprecise, and evolving meanings, a glance

at some features typical of web services will be enough to get us into coding a web

service and a client, also known as a consumer or requester. As the name suggests, a

web service is a kind of webified application, that is, an application typically delivered

over HTTP (Hyper Text Transport Protocol). A web service is thus a distributed ap-

plication whose components can be deployed and executed on distinct devices. For

instance, a stock-picking web service might consist of several code components, each

hosted on a separate business-grade server, and the web service might be consumed on

PCs, handhelds, and other devices.

Web services can be divided roughly into two groups, SOAP-based and REST-style.

The distinction is not sharp because, as a code example later illustrates, a SOAP-based

service delivered over HTTP is a special case of a REST-style service. SOAP originally

stood for Simple Object Access Protocol but, by serendipity, now may stand for Service

Oriented Architecture (SOA) Protocol. Deconstructing SOA is nontrivial but one point

is indisputable: whatever SOA may be, web services play a central role in the SOA

approach to software design and development. (This is written with tongue only partly

in cheek. SOAP is officially no longer an acronym, and SOAP and SOA can live apart

from one another.) For now, SOAP is just an XML (EXtensible Markup Language)

dialect in which documents are messages. In SOAP-based web services, the SOAP is

mostly unseen infrastructure. For example, in a typical scenario, called the request/

response message exchange pattern (MEP), the client’s underlying SOAP library sends

a SOAP message as a service request, and the web service’s underlying SOAP library

sends another SOAP message as the corresponding service response. The client and the

web service source code may provide few hints, if any, about the underlying SOAP (see

Figure 1-1).

Download at Boykma.Com

SOAP libraries SOAP libraries

Service client SOAP-based service

Request

Response

Figure 1-1. Architecture of a typical SOAP-based web service

REST stands for REpresentational State Transfer. Roy Fielding, one of the main authors

of the HTTP specification, coined the acronym in his Ph.D. dissertation to describe an

architectural style in the design of web services. SOAP has standards (under the World

Wide Web Consortium [W3C]), toolkits, and bountiful software libraries. REST has

no standards, few toolkits, and meager software libraries. The REST style is often seen

as an antidote to the creeping complexity of SOAP-based web services. This book covers

SOAP-based and REST-style web services, starting with the SOAP-based ones.

Except in test mode, the client of either a SOAP-based or REST-style service is rarely a

web browser but rather an application without a graphical user interface. The client

may be written in any language with the appropriate support libraries. Indeed, a major

appeal of web services is language transparency: the service and its clients need not

be written in the same language. Language transparency is the key to web service

interoperability; that is, the ability of web services and requesters to interact seamlessly

despite differences in programming languages, support libraries, and platforms. To

underscore this appeal, clients against our Java web services will be written in various

languages such as C#, Perl, and Ruby, and Java clients will consume services written

in other languages, including languages unknown.

There is no magic in language transparency, of course. If a SOAP-based web service

written in Java can have a Perl or a Ruby consumer, there must be an intermediary that

handles the differences in data types between the service and the requester languages.

XML technologies, which support structured document interchange and processing,

act as the intermediary. For example, in a typical SOAP-based web service, a client

transparently sends a SOAP document as a request to a web service, which transpar-

ently returns another SOAP document as a response. In a REST-style service, a client

might send a standard HTTP request to a web service and receive an appropriate XML

document as a response.

Several features distinguish web services from other distributed software systems. Here

are three:

Open infrastructure

Web services are deployed using industry-standard, vendor-independent protocols

such as HTTP and XML, which are ubiquitous and well understood. Web services

2 | Chapter 1: Java Web Services Quickstart

Download at Boykma.Com

剩余317页未读，继续阅读

qwerty090909009

粉丝: 0

Java Web 服务快速入门：从基础到实践

Java Web Services: up and running

Java Web Services Up and Running(2nd) 无水印pdf

Java Web Services: Up and Running, 1st Edition

Java Web Services - Up and Running, 2nd Edition

[JavaWeb服务：构建与运行].(Java.Web.Services：Up.and.Running).Martin.Kalin.文字版

Java Web Services Up and Running(2nd) epub

Java Web Services Up and Running, 2nd Edition 2013最新版

Java Web Services Up and Running 2009深入解析

Java.Web.Services.Up.and.Running.Feb.2009 PDF 版

Java Web Services实践：构建与运行详解

最新资源