blocks|key|5594711|text|我认为您应该为两种类型创建一个方法的控制器，并根据typeX或typeY在其中调用required+component\method。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5594712|entityMap^0|P|5|V|5|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

I think you should created controller with one method for both types, and call required component\method in it depending on <code>typeX</code> or <code>typeY</code>.

blocks|key|119776|text|如果你想绑定typeX和typeY，那么你肯定需要两个处理程序。但是，为什么我们不使用@RequestMapping的param选项呢|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|119777|@RequestMapping(method+=+RequestMethod.POST,+
++++++++value+=+"/url",+params+=+"session_type=typeX")
public+String+handleTypeX(@RequestBody+@ModelAttribute+TypeX+typeX){
++++//TODO+implement
}

@RequestMapping(method+=+RequestMethod.POST,
++++++++value+=+"/url",+params+=+"session_type=typeY")
public+String+handleTypeY(@RequestBody+@ModelAttribute+TypeY+typeY){
++++//TODO+implement
}|code-block|syntax|javascript|119778|如果您需要一些准备工作(f.e.标准化参数或手动执行模型绑定)，那么上面的方法可以与@InitBinder结合使用，但请注意，@InitBinder需要确切的ULR规则以及处理程序中的@ModelAttribute参数。|119779|编辑：在Spring+MVC中，不可能使用2个处理程序来处理确切的URL，即当方法/URL/参数/消费类型相同时。|BOLD|119780|因此，我建议使用统一的处理程序，您可以检查必要的参数，然后手动转换为相应的类。为了找到必要的类，我认为使用Strategy+pattern会更好|119781|//class+resolver+according+"session_type"+parameter
//note,+that+you+can+use+Spring+autowiring+capabilities
private+final+Map<String,+Class>+TYPES_CONTEXT+=+new+HashMap<String,+Class>(){
++++{
++++++++this.put("x",+TypeX.class);
++++++++this.put("y",+TypeY.class);
++++++++//TODO+probably+other+classes
++++}
}


@RequestMapping(method+=+RequestMethod.POST,
++++++++value+=+"/url")
public+@ResponseBody+String+handleAnyType(@RequestBody+Map<String,+String>+body){
++++String+sessionType+=+body.get("session_type");

++++//TODO+handle+case+if+sessionType+is+NULL

++++Class+convertedClass+=+TYPES_CONTEXT.get(sessionType);

++++//TODO+handle+case+if+class+is+not+found

++++Object+actualObject+=+objectMapper.convertValue(body,+convertedClass);

++++//now+we+use+reflection+for+actual+handlers,+but+you+may+refactor+this+in+the+way+you+want,+f.e.+again+with+Strategy+pattern
++++//note+that+current+approach+there+should+be+contract+for+methods+names
++++Method+actualHandler+=+this.getClass().getMethod("handle"+%2B+actualObject.getClass().getSimpleName());

++++return+(String)actualHandler.invoke(this,+actualObject);
}

public+String+handleTypeX(TypeX+typeX){
++++//TODO+implement
}

public+String+handleTypeY(TypeY+typeY){
++++//TODO+implement
}

//TODO+probably+other+methods|119782|这种方法不处理验证，并且省略了一些东西，但我相信这可能会有所帮助。|119783|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Strategy_pattern^0|6|5|C|5|17|F|1N|5|0|0|16|B|1R|B|2K|F|0|0|2|0|1H|G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@$9|14|A|15|B|C]|$9|16|A|17|B|C]|$9|18|A|19|B|C]|$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1C|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1D|8|@$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]|$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|1K|8|@$9|1L|A|1M|B|O]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1N|8|@]|D|@$9|1O|A|1P|1|1Q]]|E|$]]|$1|R|3|S|5|H|7|1R|8|@]|D|@]|E|$I|J]]|$1|T|3|U|5|6|7|1S|8|@]|D|@]|E|$]]|$1|V|3|-4|5|6|7|1T|8|@]|D|@]|E|$]]]|W|$X|$5|Y|Z|10|E|$11|12]]]]

If you want to bind <code>typeX</code> and <code>typeY</code>, then you definitely need 2 handlers. But, why wouldn't we use <code>param</code> option of <code>@RequestMapping</code>:

<pre><code>@RequestMapping(method = RequestMethod.POST, 
 value = "/url", params = "session_type=typeX")
public String handleTypeX(@RequestBody @ModelAttribute TypeX typeX){
 //TODO implement
}

@RequestMapping(method = RequestMethod.POST,
 value = "/url", params = "session_type=typeY")
public String handleTypeY(@RequestBody @ModelAttribute TypeY typeY){
 //TODO implement
}
</code></pre>

If you need some preparations (f.e. normalize params or perform model binding manually), then the approach above you may combine along with <code>@InitBinder</code>, but please note, that <code>@InitBinder</code> needs exact ULR's rules along with <code>@ModelAttribute</code> parameters in handlers.

EDIT: In Spring MVC there is no possibility to use 2 handlers for exact URL, i.e. when method/URL/params/consumes type are the same.

Thus I suggest use unified handler, where you would check necessary parameter and then manually convert into corresponding class. For finding necessary class I suppose it would be better to use <a href="http://en.wikipedia.org/wiki/Strategy_pattern" rel="nofollow">Strategy pattern</a>:

<pre><code>//class resolver according "session_type" parameter
//note, that you can use Spring autowiring capabilities
private final Map&lt;String, Class&gt; TYPES_CONTEXT = new HashMap&lt;String, Class&gt;(){
 {
 this.put("x", TypeX.class);
 this.put("y", TypeY.class);
 //TODO probably other classes
 }
}


@RequestMapping(method = RequestMethod.POST,
 value = "/url")
public @ResponseBody String handleAnyType(@RequestBody Map&lt;String, String&gt; body){
 String sessionType = body.get("session_type");

 //TODO handle case if sessionType is NULL

 Class convertedClass = TYPES_CONTEXT.get(sessionType);

 //TODO handle case if class is not found

 Object actualObject = objectMapper.convertValue(body, convertedClass);

 //now we use reflection for actual handlers, but you may refactor this in the way you want, f.e. again with Strategy pattern
 //note that current approach there should be contract for methods names
 Method actualHandler = this.getClass().getMethod("handle" + actualObject.getClass().getSimpleName());

 return (String)actualHandler.invoke(this, actualObject);
}

public String handleTypeX(TypeX typeX){
 //TODO implement
}

public String handleTypeY(TypeY typeY){
 //TODO implement
}

//TODO probably other methods
</code></pre>

This approach doesn't handle validation and some things were omitted, but I believe this might be helpful.

blocks|key|883285|text|GET不应该有请求体，或者至少在它们有请求体的情况下是the+server+side+isn't+required+to+do+anything+with+them。正如您所描述的，此接口不是RESTful。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|883286|假设您不关心这一点，请尝试创建一个控制器方法，该方法接受TypeX和TypeY的父类，或者TypeX和TypeY都实现的接口，用@SomethingMeaningfulToYou对其进行注释，然后使用web+argument+method+resolver来实例化您想要的子类。|883287|不过，这是一个破解API的技巧。|883288|entityMap|0|LINK|mutability|MUTABLE|url|http://tech.groups.yahoo.com/group/rest-discuss/message/9962|1|http://sergialmar.wordpress.com/2011/03/29/extending-handler-method-argument-resolution-in-spring-mvc/^0|R|1J|0|0|2S|S|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

GETs shouldn't have request bodies, or at least if they do, <a href="http://tech.groups.yahoo.com/group/rest-discuss/message/9962" rel="nofollow">the server side isn't required to do anything with them</a>. As you describe it, this API isn't RESTful. 

Assuming you don't care about that, try creating a controller method that takes a parent class of TypeX and TypeY, or interface that both TypeX and TypeY implement, annotate it with @SomethingMeaningfulToYou, then use a <a href="http://sergialmar.wordpress.com/2011/03/29/extending-handler-method-argument-resolution-in-spring-mvc/" rel="nofollow">web argument method resolver</a> to instantiate the child class you want. 

It's a hack around a broken API though.

blocks|key|5594803|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5594804|有2个具有相同URL但请求正文不同的POST请求|blockquote|5594805|5594806|5594807|对于RESTful接口，相同的URL应始终指示相同的资源。请求的主体可以包含该资源的不同表示。您可以为这两种不同的表示创建不同的HttpMessageContverter类。|offset|length|style|CODE|5594808|entityMap^0|0|0|0|0|1S|L|0^^$0|@$1|2|3|-4|4|5|6|N|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|O|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|P|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|Q|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|R|7|@$H|S|I|T|J|K]]|8|@]|9|$]]|$1|L|3|-4|4|5|6|U|7|@]|8|@]|9|$]]]|M|$]]

<blockquote>
 there are 2 POST requests with same URL but different request body
</blockquote>

For a RESTful interface, the same URL should always indicate the same resource. The body of a request may contain different representations of that resource. You could create different <code>HttpMessageContverter</code> classes for the two different kinds of representation.

I am working on spring REST APIs. In requirements, there are 2 POST requests with same URL but different request body. Since Spring MVC must have unique mappings across controller, I have to pre-process the request body to map to a specific POJO. 

On the basis of session_type in request body, I have to map the request to specific POJO (JSON -> JAVA POJO).

For example, if 'session_type' in request body is 'typeX' then the request should map to ClassX POJO. If 'session_type' in request body is 'typeY' then the request should map to ClassY POJO.

If there a way to do it using some kind of requestbody annotation?

Spring MVC Controller pre process request body

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我正在开发spring REST API。在requirements中，有2个具有相同URL但不同请求体的POST请求。由于Spring MVC必须具有跨控制器的唯一映射，因此我必须对请求正文进行预处理，以映射到特定的POJO。基于请求体中的session_type，我必须将请求映射到特定的POJO (JSON -> ...

问Spring MVC控制器预处理请求主体
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Spring MVC控制器预处理请求主体EN