Spring REST实战：设计与开发RESTful API指南

database

需积分: 10 180 浏览量更新于2024-07-16 收藏 4.89MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

《Spring REST》是一本实用指南，专为利用Spring框架设计和开发RESTful API提供深入讲解。本书首先从REST、HTTP以及Web基础设施的基础概念入手，引导读者理解和熟悉这些核心概念。接下来，书中详细介绍了几个关键的Spring技术组件，包括Spring Boot、Spring MVC、Spring Data JPA和Spring Security。章节一至十分别涵盖了以下几个主要知识点： 1. **第1章：REST介绍** - 为读者奠定RESTful架构的理论基础，解释RESTful原则，如资源定位、无状态性、分层系统等。 2. **第2章：Spring WebMVC入门** - 明确Spring MVC在构建RESTful应用中的角色，展示如何使用控制器、视图和模型来组织服务请求。 3. **第3章：RESTful Spring** - 展示如何在Spring框架中实现RESTful API，包括HTTP方法映射、资源接口设计和路由管理。 4. **第4章：快速启动项目：QuickPoll应用** - 通过实例演示如何用Spring构建一个实际的RESTful API应用，让读者亲身体验开发流程。 5. **第5章：错误处理** - 学习如何优雅地处理HTTP响应状态码和错误消息，确保API的健壮性。 6. **第6章：文档化REST服务** - 强调API文档的重要性，介绍如何使用工具和技术（如Swagger）来创建清晰易懂的API文档。 7. **第7章：版本控制、分页与排序** - 探讨如何处理API版本管理，以及如何优化数据返回，提升用户体验。 8. **第8章：安全性** - 讨论如何在RESTful API中实施身份验证、授权和加密等安全措施，保护数据安全。 9. **第9章：客户端和测试** - 教导读者如何使用各种工具进行API的客户端测试，确保API的稳定性和一致性。 10. **第10章：HATEOAS（ Hypermedia as the Engine of Application State）** - 解释如何通过链接关系实现自发现和自适应的API，提高客户端的灵活性。最后，附录A介绍了Windows环境下安装cURL工具，这对于测试和调试RESTful API至关重要。通过这本书，读者不仅能掌握Spring框架在构建RESTful API方面的最佳实践，还能了解到如何将这些技术无缝集成到实际项目中，实现高效、可维护的Web服务。

资源详情

资源推荐

CHAPTER 1 ■ INTRODUCTION TO REST

CrUD aND http VerBS

Data-driven applications typically use the term CRUD to indicate four basic persistence functions—

Create, Read, Update, and Delete. Some developers building REST applications have mistakenly

associated the four popular HTTP verbs GET, POST, PUT, and DELETE with CRUD semantics. The typical

association often seen is:

Create -> POST

Update -> PUT

Read -> GET

Delete -> DELETE

These correlations are true for Read and Delete operations. However, it is not as straightforward for

Create/Update and POST/PUT. As you have seen earlier in this chapter, PUT can be used to create a

resource as long as idempotency constraint is met. In the same way it was never considered non-RESTful

if POST is used for update (http://roy.gbiv.com/untangled/2009/it-is-okay-to-use-post). It is

also possible for a client to use PATCH for updating a resource.

Therefore, it is important for API designers to use the right verbs for a given operation than simply using

a 1-1 mapping with CRUD.

HTTP Status Codes

The HTTP Status codes allow a server to communicate the results of processing a client’s request. These

status codes are grouped into the following categories:

• Informational Codes—Status codes indicating that the server has received the

request but hasn’t completed processing it. These intermediate response codes are

in the 100 series.

• Success Codes—Status codes indicating that the request has been successfully

received and processed. These codes are in the 200 series.

• Redirection Codes—Status codes indicating that the request has been processed, but

the client must perform an additional action to complete the request. These actions

typically involve redirecting to a different location to get the resource. These codes

are in the 300 series.

• Client Error Codes—Status codes indicating that there was an error or a problem

with client’s request. These codes are in the 400 series.

• Server Error Codes—Status codes indicating that there was an error on the server

while processing the client’s request. These codes are in the 500 series.

The HTTP Status codes play an important role in REST API design as meaningful codes help

communicate the right status, enabling the client to react appropriately. Table1-2 shows some of the

important status codes into which you typically run.

CHAPTER 1 ■ INTRODUCTION TO REST

Richardson’s Maturity Model

The Richardson’s Maturity Model (RMM), developed by Leonard Richardson, classifies REST-based Web

services on how well they adhere to REST principles. Figure1-1 shows the four levels of this classification.

Table 1-2. HTTP status codes and their descriptions

Status Code Description

100 (Continue) Indicates that the server has received the first part of the request and the rest

of the request should be sent.

200 (OK) Indicates that all went well with the request.

201 (Created) Indicates that request was completed and a new resource got created.

202 (Accepted) Indicates that request has been accepted but is still being processed.

204 (No Content) Indicates that the server has completed the request and has no entity body to

send to the client.

301 (Moved Permanently) Indicates that the requested resource has been moved to a new location and

a new URI needs to be used to access the resource.

400 (Bad Request) Indicates that the request is malformed and the server is not able to

understand the request.

401 (Unauthorized) Indicates that the client needs to authenticate before accessing the resource.

If the request already contains client’s credentials, then a 401 indicates

invalid credentials (e.g., bad password).

403 (Forbidden) Indicates that the server understood the request but is refusing to fulfill it.

This could be because the resource is being accessed from a blacklisted IP

address or outside the approved time window.

404 (Not Found) Indicates that the resource at the requested URI doesn’t exist.

406 (Not Acceptable) Indicates that the server is capable of processing the request; however, the

generated response may not be acceptable to the client. This happens when

the client becomes too picky with its accept headers.

500 (Internal Server Error) Indicates that there was an error on the server while processing the request

and that the request can’t be completed.

503 (Service Unavailable) Indicates that the request can’t be completed, as the server is overloaded or

going through scheduled maintenance.

剩余194页未读，继续阅读

jiangdmdr

粉丝: 57
资源: 771

Spring REST实战：设计与开发RESTful API指南

Spring REST Docs API（Spring REST Docs 开发文档）.CHM

spring rest 增删改查（put\delete\post\get）简单示例详细讲解

Spring REST权威指南：版权作品

Spring REST指南：设计与开发实战

Spring REST权威指南：2015年最新出版

Spring REST微服务下的分布式事务与JTA详解

Spring安全: 开发安全的REST API

Spring Boot Security中实现安全的REST API

构建REST客户端：使用Spring MVC消费RESTful服务

RESTful Web服务与Spring MVC：构建REST API

RESTful服务与Spring5：构建简单的REST API

Spring REST Docs

spring 2021年外文参考文献

spring 技术实战4pdf

spring获取返回头

9.哪个说法最能描述 Spring MVC 中的 REST 特性?(选一项) A.Spring MVC的 REST 功能不依赖于JAX-RS 标准 B.Spring MVC 提供其JAX-RS 实现 C.Spring MVC 的 REST 功能可以依赖任何JAX-RS 实现

有没有springboot的开源的app项目

java主流的api文档框架

最新资源