JAX-RS 2.0：RESTful Web服务规范详解

需积分: 9 32 浏览量更新于2024-07-26 收藏 552KB PDF 举报

"基于REST的Web服务规范2.0版本，是JAX-RS(Java API for RESTful Web Services)的第二个主要版本，用于定义如何在Java平台上构建RESTful服务。该规范由Oracle Corporation的Santiago Pericas-Geertsen和Marek Potociar编辑，并于2012年9月26日公开审查。" 本文将详细介绍基于REST的Web服务规范2.0版本，特别是与JAX-RS的相关内容。 REST（Representational State Transfer）是一种网络应用程序的设计风格和开发方式，强调使用HTTP协议中的方法（如GET、POST、PUT、DELETE等）来操作资源，以实现简洁、高效和可扩展的接口。JAX-RS作为Java平台上的RESTful服务标准，简化了在Java应用程序中创建RESTful服务的过程。 JAX-RS 2.0版本引入了多项改进和新特性，包括： 1. **注解增强**：开发者可以使用注解如`@Path`、`@GET`、`@POST`等直接在Java类和方法上声明路由和HTTP操作。这使得服务的定义更加直观和简洁。 2. **客户端API**：除了服务器端的支持，JAX-RS 2.0还提供了客户端API，允许开发者直接在代码中创建和执行REST请求，进行数据交互。 3. **类型安全的HTTP响应**：通过`ResponseBuilder`，开发者可以构建具有指定状态码和头部的响应，增强了对HTTP协议的控制。 4. **异步处理**：引入了`@Suspended`注解，支持非阻塞I/O，提高了服务的并发性能。 5. **链接管理**：通过`Link`和`LinkBuilder`，服务可以生成和解析包含HATEOAS（超媒体作为应用程序状态的引擎）链接的响应，增强了系统的自描述性。 6. **提供者和拦截器**：开发者可以编写自定义的提供者（如消息BodyReader/Writer）和拦截器（用于请求和响应处理），以扩展JAX-RS的功能。 7. **统一异常处理**：通过`ExceptionMapper`接口，开发者可以定义如何将未捕获的异常转换为HTTP响应。 8. **依赖注入集成**：JAX-RS 2.0支持JSR 330（Dependency Injection）规范，可以与其他依赖注入框架如CDI（Contexts and Dependency Injection）无缝集成。 9. **JSON-P支持**：增加了对JSON Processing (JSR 353)的内置支持，简化了JSON数据的序列化和反序列化。 10. **XML处理**：通过JAXB或StAX，JAX-RS 2.0提供了一种统一的方式来处理XML数据。 JAX-RS 2.0版本的发布进一步提升了Java开发者构建RESTful服务的效率和灵活性，同时保持了与现有Java生态系统的良好兼容性。通过遵循这个规范，开发者能够构建出符合REST原则、高度模块化且易于维护的Web服务。

1.7. Acknowledgements

− Hamid Ben Malek (Fujitsu Limited)

− Ryan J. McDonough (Individual Member)

− Felix Meschberger (Day Software, Inc.)

− David Orchard (BEA Systems)

− Dhanji R. Prasanna (Individual Member)

− Julian Reschke (Individual Member)

− Jan Schulz-Hofen (Individual Member)

− Joel Smith (IBM)

− Stefan Tilkov (innoQ Deutschland GmbH)

1.7 Acknowledgements

During the course of this JSR we received many excellent suggestions. Special thanks to Martin Matula,

Gerard Davison, Jakub Podlesak and Pavel Bucek from Oracle as well as Pete Muir and Emmanuel Bernard

from Red Hat. Also to Gunnar Morling and Ron Sigal (Red Hat) for their suggestions on how to improve

resource validation, and to Mattias Arthursson for his insights on hypermedia.

During the course of the JSR 311 we received many excellent suggestions on the JSR and Jersey (RI)

mailing lists, thanks in particular to James Manger (Telstra) and Reto Bachmann-Gm

ur (Trialox) for their

contributions. The following individuals (all Sun Microsystems at the time) have also made invaluable

technical contributions: Roberto Chinnici, Dianne Jiao (TCK), Ron Monzillo, Rajiv Mordani, Eduardo

Pelegri-Llopart, Jakub Podlesak (RI) and Bill Shannon.

The GenericEntity class was inspired by the Google Guice TypeLiteral class. Our thanks to Bob Lee

and Google for donating this class to JAX-RS.

September 26, 2012 JAX-RS 5

Chapter 2. Applications

type of endpoint required. An implementation MAY support zero or more endpoint types of any desired

type.

How the resulting endpoint class instance is used to publish the application is outside the scope of this

speciﬁcation.

2.3.1.1 JAX-WS

An implementation that supports publication via JAX-WS MUST support createEndpoint with an end-

point type of javax.xml.ws.Provider. JAX-WS describes how a Provider based endpoint can be

published in an SE environment.

2.3.2 Servlet

A JAX-RS application is packaged as a Web application in a .war ﬁle. The application classes are packaged

in WEB-INF/classes or WEB-INF/lib and required libraries are packaged in WEB-INF/lib. See the

Servlet speciﬁcation for full details on packaging of web applications.

It is RECOMMENDED that implementations support the Servlet 3 framework pluggability mechanism to

enable portability between containers and to avail themselves of container-supplied class scanning facilities.

When using the pluggability mechanism the following conditions MUST be met:

• If no Application subclass is present, JAX-RS implementations are REQUIRED to dynamically

add a servlet and set its name to

javax.ws.rs.core.Application

and to automatically discover all root resource classes and providers which MUST be packaged with

the application. Additionally, the application MUST be packaged with a web.xml that speciﬁes a

servlet mapping for the added servlet. An example of such a web.xml ﬁle is:

1 <web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee"

2 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

3 xsi:schemaLocation="http://java.sun.com/xml/ns/javaee

4 http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">

5 <servlet>

6 <servlet-name>javax.ws.rs.core.Application</servlet-name>

7 </servlet>

8 <servlet-mapping>

9 <servlet-name>javax.ws.rs.core.Application</servlet-name>

10 <url-pattern>/myresources/

</url-pattern>

11 </servlet-mapping>

12 </web-app>

• If an Application subclass is present:

– If there is already a servlet that handles this application. That is, a servlet that has an initialization

parameter named

javax.ws.rs.Application

whose value is the fully qualiﬁed name of the Application subclass, then no additional con-

ﬁguration steps are required by the JAX-RS implementation.

8 JAX-RS September 26, 2012

剩余86页未读，继续阅读

scobala

粉丝: 0
资源: 3

JAX-RS 2.0：RESTful Web服务规范详解

webservice规范参考

webservice开发所需要的包

WebserviceStudio2.0

webService

webservice

基于 cxf 2.7.5 开发的 webservice [soap restful]

JAX-RS cxf web服务 rest简单增删改查 集成spring webService

webservice 学习

Smart2.0 用户手册

wsdl-webservice

最新资源

JAX-RS cxf web服务 rest简单增删改查集成spring webService