JAX-RS 发布多个对象
我有一个方法;
@POST
@Path("test")
@Consumes(MediaType.APPLICATION_JSON)
public void test(ObjectOne objectOne, ObjectTwo objectTwo)
现在我知道我可以以 json 格式发布单个对象,只需将其放入正文中即可。 但是可以做多个对象吗?如果是这样,怎么办?
I have a method;
@POST
@Path("test")
@Consumes(MediaType.APPLICATION_JSON)
public void test(ObjectOne objectOne, ObjectTwo objectTwo)
Now I know I can post a single object in json format, just putting it into the body.
But is it possible to do multiple objects? If so, how?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(9)
正如 Tarlog 所正确指出的那样,您不能使用您的方法。
但是,您可以这样做:
或这样做:
此外,您始终可以将您的方法与 GET 参数结合起来:
You can not use your method like this as correctly stated by Tarlog.
However, you can do this:
or this:
Furthermore, you can always combine your method with GET parameters:
答案是否。
原因很简单:这是关于您可以在方法中接收的参数。它们必须与请求相关。正确的?因此它们必须是 headers 或 cookie 或查询参数或矩阵参数或路径参数或请求正文。 (为了讲述完整的故事,还有称为上下文的其他类型的参数)。
现在,当您在请求中收到 JSON 对象时,您会在请求正文中收到它。该请求可能有多少个主体?唯一的一个。所以你只能接收一个 JSON 对象。
The answer is no.
The reason is simple: This about the parameters you can receive in a method. They must be related to the request. Right? So they must be either headers or cookies or query parameters or matrix parameters or path parameters or request body. (Just to tell the complete story there is additional types of parameters called context).
Now, when you receive JSON object in your request, you receive it in a request body. How many bodies the request may have? One and only one. So you can receive only one JSON object.
如果我们看看 OP 试图做什么,他/她正在尝试发布两个(可能不相关的)JSON 对象。首先,任何尝试将一部分作为正文发送,并将一部分作为其他参数发送的解决方案,IMO,都是可怕的解决方案。 POST 数据应该放在正文中。仅仅因为某件事有效就去做它是不对的。某些解决方法可能违反基本的 REST 原则。
我看到一些解决方案
1. 使用 application/x-www-form-urlencoded
另一种选择是仅使用
application/x- www-form-urlencoded
。我们实际上可以拥有 JSON 值。例如,要使其正常工作,我们需要的一件事是使用
ParamConverterProvider
才能使其正常工作。下面是 Jersey 团队的 Michal Gadjos 实现的一个(发现 此处有解释)。如果您不扫描资源和提供程序,只需注册该提供程序,上面的示例就应该可以工作。
2.使用Multipart
没有人提到的一种解决方案是使用
此处)
这是一个使用 Jersey 的示例(请参阅官方文档
MultipartFeature
资源类
现在,对于某些客户端来说,棘手的部分是没有办法设置每个正文部分的
Content-Type
,而这是上述内容所必需的工作。多部分提供程序将根据每个部分的类型查找消息正文阅读器。如果它没有设置为application/json
或类型,Foo
或Bar
有一个阅读器,这将会失败。我们将在这里使用 JSON。除了有一个可用的阅读器之外,没有额外的配置。我会用杰克逊。使用以下依赖项,不需要其他配置,因为将通过类路径扫描发现提供程序。现在测试。我将使用 cURL。您可以看到我使用
type
为每个部分显式设置了Content-Type
。-F
表示不同的部分。 (请参阅帖子的最底部,了解请求正文的实际外观。)结果完全符合我们的预期。如果您查看资源方法,我们所做的就是返回从两个 JSON 对象收集的字符串
foo.foo + "; " + bar.bar
。您可以在下面的链接中看到一些使用不同 JAX-RS 客户端的示例。您还将看到来自这些不同 JAX-RS 实现的一些服务器端示例。每个链接中都应该有一个指向该实现的官方文档的链接
还有其他 JAX-RS那里有实现,但您需要自己找到它的文档。以上三个是我唯一有经验的。
就 Javascript 客户端而言,我看到的大多数示例(例如 其中一些 涉及设置
Content-Type
为 undefined/false(使用FormData
),让浏览器处理它,但这对我们不起作用,因为浏览器不会设置Content-Type
。 部分的默认类型是text/plain
。每个 手动,我将发布一个示例(从 此处 获得一些帮助。我将使用 Angular,但是 grunt构建实体主体的工作将是普通的旧 Javascript。
有趣的部分是 createRequest 函数,这是我们构建多部分的地方,设置每个部分的 Content-Type 。到
application/json
,并将字符串化的foo
和bar
对象连接到每个部分。如果您不熟悉多部分格式请参阅此处了解更多信息。另一个有趣的部分是标题。我们将其设置为multipart/form-data
。下面是结果。在 Angular 中,我只是使用
$scope.result = response.data
在 HTML 中显示结果。您看到的按钮只是提出请求。您还将在 firebug3. 只需将它们包装在单个父对象中
此选项应该是不言自明的,正如其他人已经提到的那样。
If we look at what the OP is trying to do, he/she is trying to post two (possibly unrelated) JSON objects. First any solution to try and send one part as the body, and one part as some other param, IMO, are horrible solutions. POST data should go in the body. It's not right to do something just because it works. Some work-arounds might be violating basic REST principles.
I see a few solutions
1. Use application/x-www-form-urlencoded
Another option is to just use
application/x-www-form-urlencoded
. We can actually have JSON values. For examleThe one thing we need to get this to work is a
ParamConverterProvider
to get this to work. Below is one that has been implemented by Michal Gadjos of the Jersey Team (found here with explanation).If you aren't scanning for resource and providers, just register this provider, and the above example should work.
2. Use Multipart
One solution that no one has mentioned, is to use multipart. This allows us to send arbitrary parts in a request. Since each request can only have one entity body, multipart is the work around, as it allows to have different parts (with their own content types) as part of the entity body.
Here is an example using Jersey (see official doc here)
Dependency
Register the
MultipartFeature
Resource class
Now the tricky part with some clients is that there isn't a way to set the
Content-Type
of each body part, which is required for the above to work. The multipart provider will look up message body reader, based on the type of each part. If it's not set toapplication/json
or a type, theFoo
orBar
has a reader for, this will fail. We will use JSON here. There's no extra configuration but to have a reader available. I'll use Jackson. With the below dependency, no other configuration should be required, as the provider will be discovered through classpath scanning.Now the test. I will be using cURL. You can see I explicitly set the
Content-Type
for each part withtype
. The-F
signifies to different part. (See very bottom of the post for an idea of how the request body actually looks.)The result is exactly as we expected. If you look at the resource method, all we do is return this string
foo.foo + "; " + bar.bar
, gathered from the two JSON objects.You can see some examples using some different JAX-RS clients, in the links below. You will also see some server side example also from those different JAX-RS implementations. Each link should have somewhere in it a link to the official documentation for that implementation
There are other JAX-RS implementations out there, but you will need to find the documentation for it yourself. The above three are the only ones I have experience with.
As far as Javascript clients, most of the example I see (e.g. some of these involve setting the
Content-Type
to undefined/false (usingFormData
), letting the Browser handle the it. But this will not work for us, as the Browser will not set theContent-Type
for each part. And the default type istext/plain
.I'm sure there are libraries out there that allow setting the type for each part, but just to show you how it can be done manually, I'll post an example (got a little help from here. I'll be using Angular, but the grunt work of building the entity body will be plain old Javascript.
The interesting part is the
createRequest
function. This is where we build the multipart, setting theContent-Type
of each part toapplication/json
, and concatenating the stringifiedfoo
andbar
objects to each part. If you are unfamiliar multipart format see here for more info. The other interesting part is the header. We set it tomultipart/form-data
.Below is the result. In Angular I just used the result to show in the HTML, with
$scope.result = response.data
. The button you see was just to make the request. You will also see the request data in firebug3. Just wrap them in a single parent object
This option should be self explanatory, as others have already mentioned.
在这种情况下通常采用下一种方法:
The next approach is usually applied in this kind of cases:
正如 Tarlog 所解释的,您不能将两个单独的对象放入一个 POST 调用中。
无论如何,您可以创建包含前两个对象的第三个容器对象,并在 POS 调用中传递该对象。
You can't put two separate objects in one single POST call as explained by Tarlog.
Anyway you could create a third container object that contains the first two objects and pass that one within the POS call.
我也面临过这些问题。也许这会有所帮助。
I have also faced with these problem. Maybe this will help.
这可以通过声明 POST 方法来接受对象数组来完成。像这样的例子
It can be done by having the POST method declared to accept array of objects. Example like this
更改@Consumes(MediaType.APPLICATION_JSON)
到@Consumes({MediaType.APPLICATION_FORM_URLENCODED})
然后你可以将多个对象放入body中
Change @Consumes(MediaType.APPLICATION_JSON)
to @Consumes({MediaType.APPLICATION_FORM_URLENCODED})
Then you can putting multiple objects into the body
我的解决方案是为CXF编写的,看起来很简单。
使用 io.restassurred 的测试代码:
My solution is written for CXF, it appears to be quite simple.
The test code for this with io.restassurred: