The JAX-RS specification (JSR-311) provides a standard means of creating RESTful services over HTTP. There are several JAX-RS implementations: Jersey, RESTEasy, Wink. JAXB (JSR-222) is the standard binding layer (objects to/from XML) for JAX-RS, and there are several implementations: MOXy, Metro, JaxMe, etc.
These implementations are also come pre-bundled with Java EE application servers (i.e. GlassFish and WebLogic contain Jersey).
Here is an example I put together using Jersey & MOXy in GlassFish:
My advice would be to not use a binding tool at all. Just deal with the fact that what you are sending over the wire is in fact XML. The Spring Web Services reference manual describes the rationale behind this, which is called 'contract first', right here
I understand that what you are looking to write is not a SOAP service, but a REST service. That doesn't matter for the point I am making against using a binding tool, the principle of 'contract first' still applies.
发布评论
评论（5）
JAX-RS 规范 (JSR-311) 提供了通过 HTTP 创建 RESTful 服务的标准方法。有几种 JAX-RS 实现：Jersey、RESTEasy、Wink。 JAXB (JSR-222) 是 JAX-RS 的标准绑定层（与 XML 之间的对象），有多种实现： MOXy、Metro、JaxMe 等。
这些实现也预先与 Java EE 应用程序服务器捆绑在一起（即 GlassFish 和 WebLogic 包含 Jersey）。
这是我使用 Jersey & 组合在一起的示例。 GlassFish 中的 MOXy：
The JAX-RS specification (JSR-311) provides a standard means of creating RESTful services over HTTP. There are several JAX-RS implementations: Jersey, RESTEasy, Wink. JAXB (JSR-222) is the standard binding layer (objects to/from XML) for JAX-RS, and there are several implementations: MOXy, Metro, JaxMe, etc.
These implementations are also come pre-bundled with Java EE application servers (i.e. GlassFish and WebLogic contain Jersey).
Here is an example I put together using Jersey & MOXy in GlassFish:
我们最近使用 Apache CXF 做了一些工作，并发现了它的 JAX-RS支持简单并允许我们编写非常 DRY 友好的代码。
有一定程度的灵活性，例如可以选择几个不同的数据绑定层。
We've done some work recently using Apache CXF, and found its JAX-RS support to be simple and allow us to write very DRY friendly code.
There is a reasonable amount of flexibility, e.g. several different data binding layers to choose from.
XStream 怎么样？ http://x-stream.github.io/
XStream 是一个将对象序列化为 XML 的简单库然后再回来。
How about XStream? http://x-stream.github.io/
XStream is a simple library to serialize objects to XML and back again.
我喜欢 http://www.restlet.org/
I like http://www.restlet.org/
我的建议是根本不要使用绑定工具。只需要面对这样一个事实：您通过网络发送的实际上是 XML。 Spring Web Services 参考手册描述了其背后的基本原理，称为“契约优先”，就在这里
我知道您要编写的不是 SOAP 服务，而是 REST 服务。这对于我反对使用绑定工具的观点来说并不重要，“合同第一”的原则仍然适用。
祝你好运！
My advice would be to not use a binding tool at all. Just deal with the fact that what you are sending over the wire is in fact XML. The Spring Web Services reference manual describes the rationale behind this, which is called 'contract first', right here
I understand that what you are looking to write is not a SOAP service, but a REST service. That doesn't matter for the point I am making against using a binding tool, the principle of 'contract first' still applies.
Good luck!