blocks|key|19547|text|JAX规范(JSR-311)提供了一种通过HTTP创建RESTful服务的标准方法。有几种JAX实现：泽西岛、RESTEasy、Wink.JAXB+(JSR-222)是JaxMe的标准绑定层(对象)，有几种实现：MOXy、Metro、JaxMe等。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|19548|这些实现也与Java应用服务器捆绑在一起(即GlassFish和WebLogic包含泽西)。|19549|下面是我在GlassFish中使用泽西&GlassFish创建的一个示例：|19550|第一部分-数据库|unordered-list-item|19551|第2部分-将数据库映射到JPA实体|19552|第3部分-将JPA实体映射到XML+(使用JAXB)|19553|第4部分-+RESTful服务|19554|第5部分-客户|19555|entityMap|0|LINK|mutability|MUTABLE|url|http://jersey.java.net/|1|http://www.eclipse.org/eclipselink/moxy.php|2|http://glassfish.java.net/|3|http://bdoughan.blogspot.com/2010/08/creating-restful-web-service-part-15.html|4|http://bdoughan.blogspot.com/2010/08/creating-restful-web-service-part-25.html|5|http://bdoughan.blogspot.com/2010/08/creating-restful-web-service-part-35.html|6|http://bdoughan.blogspot.com/2010/08/creating-restful-web-service-part-45.html|7|http://bdoughan.blogspot.com/2010/08/creating-restful-web-service-part-55.html^0|0|3|1X|4|1F|3|0|2Y|4|1|0|M|9|2|0|0|0|8|3|0|0|H|4|0|0|Q|5|0|0|F|6|0|0|7|7|0^^$0|@$1|2|3|4|5|6|7|1G|8|@$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]]|D|@$9|1L|A|1M|1|1N]|$9|1O|A|1P|1|1Q]]|E|$]]|$1|F|3|G|5|6|7|1R|8|@]|D|@$9|1S|A|1T|1|1U]]|E|$]]|$1|H|3|I|5|6|7|1V|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1W|8|@]|D|@$9|1X|A|1Y|1|1Z]]|E|$]]|$1|M|3|N|5|L|7|20|8|@]|D|@$9|21|A|22|1|23]]|E|$]]|$1|O|3|P|5|L|7|24|8|@]|D|@$9|25|A|26|1|27]]|E|$]]|$1|Q|3|R|5|L|7|28|8|@]|D|@$9|29|A|2A|1|2B]]|E|$]]|$1|S|3|T|5|L|7|2C|8|@]|D|@$9|2D|A|2E|1|2F]]|E|$]]|$1|U|3|-4|5|6|7|2G|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]|12|$5|X|Y|Z|E|$10|13]]|14|$5|X|Y|Z|E|$10|15]]|16|$5|X|Y|Z|E|$10|17]]|18|$5|X|Y|Z|E|$10|19]]|1A|$5|X|Y|Z|E|$10|1B]]|1C|$5|X|Y|Z|E|$10|1D]]|1E|$5|X|Y|Z|E|$10|1F]]]]

The JAX-RS specification (JSR-311) provides a standard means of creating RESTful services over HTTP. There are several JAX-RS implementations: <a href="http://jersey.java.net/" rel="nofollow">Jersey</a>, RESTEasy, Wink. JAXB (JSR-222) is the standard binding layer (objects to/from XML) for JAX-RS, and there are several implementations: <a href="http://www.eclipse.org/eclipselink/moxy.php" rel="nofollow">MOXy</a>, Metro, JaxMe, etc.

These implementations are also come pre-bundled with Java EE application servers (i.e. <a href="http://glassfish.java.net/" rel="nofollow">GlassFish</a> and WebLogic contain Jersey).

Here is an example I put together using Jersey &amp; MOXy in GlassFish:

<ul>
<li><a href="http://bdoughan.blogspot.com/2010/08/creating-restful-web-service-part-15.html" rel="nofollow">Part 1 - The Database</a></li>
<li><a href="http://bdoughan.blogspot.com/2010/08/creating-restful-web-service-part-25.html" rel="nofollow">Part 2 - Mapping the Database to JPA Entities</a></li>
<li><a href="http://bdoughan.blogspot.com/2010/08/creating-restful-web-service-part-35.html" rel="nofollow">Part 3 - Mapping JPA entities to XML (using JAXB)</a></li>
<li><a href="http://bdoughan.blogspot.com/2010/08/creating-restful-web-service-part-45.html" rel="nofollow">Part 4 - The RESTful Service</a></li>
<li><a href="http://bdoughan.blogspot.com/2010/08/creating-restful-web-service-part-55.html" rel="nofollow">Part 5 - The Client</a></li>
</ul>

blocks|key|20440|text|我们最近使用Apache做了一些工作，发现它的贾克斯-RS支持很简单，允许我们编写非常枯燥的友好代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|20441|有一定的灵活性，例如几个不同的数据绑定层可供选择。|20442|entityMap|0|LINK|mutability|MUTABLE|url|http://cxf.apache.org/docs/jax-rs.html^0|N|6|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

We've done some work recently using Apache CXF, and found its <a href="http://cxf.apache.org/docs/jax-rs.html" rel="nofollow">JAX-RS</a> 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.

blocks|key|62706|text|XStream怎么样？http://x-stream.github.io/？|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|62707|XStream是一个简单的库，可以将对象序列化为XML并再次返回。|62708|entityMap|0|LINK|mutability|MUTABLE|url|http://x-stream.github.io/^0|B|Q|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

How about XStream? <a href="http://x-stream.github.io/" rel="nofollow">http://x-stream.github.io/</a>

XStream is a simple library to serialize objects to XML and back again.

blocks|key|62687|text|我喜欢http://www.restlet.org/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|62688|entityMap|0|LINK|mutability|MUTABLE|url|http://www.restlet.org/^0|3|N|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I like <a href="http://www.restlet.org/" rel="nofollow">http://www.restlet.org/</a>

blocks|key|19574|text|我的建议是不要使用绑定工具。只需处理这样一个事实，即您通过网络发送的实际上是XML。Services参考手册描述了这背后的原理，称为‘契约优先’，就在这里|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|19575|我理解您想要编写的不是SOAP服务，而是REST服务。对于我反对使用绑定工具的观点来说，这并不重要，“合同优先”的原则仍然适用。|19576|祝好运!|19577|entityMap|0|LINK|mutability|MUTABLE|url|http://static.springsource.org/spring-ws/site/reference/html/why-contract-first.html^0|21|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

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', <a href="http://static.springsource.org/spring-ws/site/reference/html/why-contract-first.html" rel="nofollow">right here</a>

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!

I need to expose some services of the web application to remote clients via XML interfaces over http.
A number of provided services is limited (3-7), both request and response should be kept simple and do not require any special data types or cross-entity relations. 

My goal is to keep the code clean and clear and have robust and performant application.
I would really appreciate your advices regarding the proper XML binding\processing tool to be used for that task.

UPD: My bad, haven't mentioned that <a href="http://www.restlet.org/" rel="nofollow">restlet</a> is required for implementation, however, as far as I am concerned, it does not impose any restrictions on the xml tool to be used.

Thanks in advance.

Proper tool for simple XML interfaces

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我需要通过http上的XML接口向远程客户端公开web应用程序的一些服务。提供的服务数量有限(3-7)，请求和响应都应保持简单，不需要任何特殊的数据类型或跨实体关系。我的目标是保持代码的整洁和清晰，并具有健壮和可执行的应用程序。我非常感谢您对用于该任务的适当XML绑定\处理工具的建议。UPD:我的坏消息，没有提到是实现所必需的，但是，就我而言，它并没有对要使用的工具施加任何限制。提前谢谢。

问简单XML接口的适当工具
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问简单XML接口的适当工具EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问简单XML接口的适当工具
EN