区分Jersey，Jackson和JaxB API [英] Differentiating the Jersey, Jackson, and JaxB APIs

问题描述

嗨：我一直在内部使用Jackson进行JSON处理，我希望将这些对象作为Jsons提供给外部API（REST）（现在，它们作为java对象存储在内部）。

Hi : I've been using Jackson for JSON processing internally , and I want to serve these objects as Jsons to an external API (REST) (now, they are stored internally as java objects) .

显而易见的实现是编写某种查询引擎来读取请求，从底层数据存储中检索对象，然后使用Jackson将它们序列化为Jsons。

The obvious implementation would be to write some kind of query engine that reads requests, retrieves objects from the underlying data store, and then serializes them into Jsons using Jackson.

然而，我开始意识到已经有一些API已经可以用来组装这样的Web服务，负责处理很多平凡的细节（安全性，查询解析，REST协调）。例如，似乎可以使用泽西注释来定义REST服务....

However I'm starting to realize that there are APIs that already can be used to assemble such web services , taking care of a lot of the mundane details (security, query parsing, REST coordination) . For example, it appears that jersey annotations can be used to define REST services ....

所以我的问题是：Java EE JSON的最新技术水平是什么基于Web的服务，以及这些服务用作数据存储的内容（即明文？RDBMS？对象数据服务？）

So my question is : what are the state of the art in Java EE JSON based web services, and what do these services use as data stores (I.e. Plaintext? RDBMS? Object data services?)

最重要的是......什么是xml和json数据映射的不同apis之间的功能差异，即jersey / Jackson / JaxB？

推荐答案

除了使用杰克逊的泽西岛（和其他JAX-RS一样，像RESTeasy一样）你可能也会受益于使用像 jDBI 这样的东西首先在POJO中绑定关系数据。
它做了很多更大的ORM（比如Hibernate），但更容易用于大多数常见任务。

Aside from Jersey (and other JAX-RS impls like RESTeasy), which use Jackson, you might also benefit from using something like jDBI for binding relational data in POJOs first. It does many things bigger ORMs (like Hibernate) do, but is simpler to use for most common tasks.

或者如果您更喜欢Hibernate，请使用 Jackson Hibernate模块处理一些边缘情况，可能在读取/写入POHO时为JSON。

Or if you prefer Hibernate, use Jackson Hibernate module to handle some edge cases there may be when reading/writing POHOs as JSON.

这篇关于区分Jersey，Jackson和JaxB API的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！