blocks|key|245622|text|您的@POST方法应该接受JSON对象而不是字符串。Jersey使用JAXB来支持编组和解组JSON对象(参见the+jersey+docs+for+details)。创建类，如下所示：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|245623|@XmlRootElement
public+class+MyJaxBean+{
++++@XmlElement+public+String+param1;
++++@XmlElement+public+String+param2;
}|code-block|syntax|javascript|245624|然后，您的@POST方法将如下所示：|245625|@POST+@Consumes("application/json")
@Path("/create")
public+void+create(final+MyJaxBean+input)+{
++++System.out.println("param1+=+"+%2B+input.param1);
++++System.out.println("param2+=+"+%2B+input.param2);
}|245626|此方法期望接收JSON对象作为HTTP+POST的主体。JAX-RS将HTTP消息的内容主体作为一个未注释的参数传递--在本例中为input。实际的消息看起来像这样：|245627|POST+/create+HTTP/1.1
Content-Type:+application/json
Content-Length:+35
Host:+www.example.com

{"param1":"hello","param2":"world"}|245628|由于显而易见的原因，以这种方式使用JSON非常常见。但是，如果您在JavaScript以外的其他地方生成或使用它，则必须小心正确地转义数据。在JAX-RS中，可以使用MessageBodyReader和MessageBodyWriter来实现这一点。我相信Jersey已经有了针对所需类型(例如，Java原语和JAXB包装类)以及JSON的实现。JAX-RS支持许多其他的数据传递方法。这些不需要创建新的类，因为数据是使用简单的参数传递来传递的。|245629|245630|<FORM>+超文本标记语言|BOLD|245631|这些参数将使用@FormParam进行注释|245632|@POST
@Path("/create")
public+void+create(@FormParam("param1")+String+param1,
+++++++++++++++++++@FormParam("param2")+String+param2)+{
++++...
}|245633|浏览器将使用"application/x-www-form-urlencoded"对表单进行编码。JAX-RS运行时将负责解码主体并将其传递给方法。下面是你应该在网上看到的内容：|245634|POST+/create+HTTP/1.1
Host:+www.example.com
Content-Type:+application/x-www-form-urlencoded;charset=UTF-8
Content-Length:+25

param1=hello&param2=world|245635|在本例中，内容为。|245636|如果您不知道FormParam的名称，可以执行以下操作：|245637|@POST+@Consumes("application/x-www-form-urlencoded")
@Path("/create")
public+void+create(final+MultivaluedMap<String,+String>+formParams)+{
++++...
}|245638|245639|+Headers|245640|如果你想通过HTTP头传递参数，你可以使用@HeaderParam注解：|245641|@POST
@Path("/create")
public+void+create(@HeaderParam("param1")+String+param1,
+++++++++++++++++++@HeaderParam("param2")+String+param2)+{
++++...
}|245642|下面是HTTP消息的样子。请注意，这篇文章没有正文。|245643|POST+/create+HTTP/1.1
Content-Length:+0
Host:+www.example.com
param1:+hello
param2:+world|245644|我不会使用这种方法来传递泛化参数。但是，如果您需要访问特定HTTP标头的值，那么它非常方便。|245645|245646|HTTP查询参数|245647|此方法主要用于HTTP+GETs，但也同样适用于POST。它使用@QueryParam注释。|245648|@POST
@Path("/create")
public+void+create(@QueryParam("param1")+String+param1,
+++++++++++++++++++@QueryParam("param2")+String+param2)+{
++++...
}|245649|与前面的技术一样，通过查询字符串传递参数不需要消息体。下面是HTTP消息：|245650|POST+/create?param1=hello&param2=world+HTTP/1.1
Content-Length:+0
Host:+www.example.com|245651|您必须特别小心在客户端正确地执行encode+query+parameters操作。由于某些代理实施的URL长度限制以及与编码相关的问题，使用查询参数可能会出现问题。|245652|245653|HTTP路径参数|245654|path参数与查询参数类似，只是它们嵌入在HTTP资源路径中。这种方法似乎在今天很受欢迎。这对HTTP缓存有影响，因为路径是真正定义HTTP资源的路径。由于修改了@Path注释并使用了@PathParam，因此代码看起来与其他代码略有不同|245655|@POST
@Path("/create/{param1}/{param2}")
public+void+create(@PathParam("param1")+String+param1,
+++++++++++++++++++@PathParam("param2")+String+param2)+{
++++...
}|245656|该消息类似于查询参数版本，不同之处在于参数的名称不包含在消息中的任何位置。|245657|POST+/create/hello/world+HTTP/1.1
Content-Length:+0
Host:+www.example.com|245658|此方法与查询参数版本具有相同的编码问题。所以你也要小心，Path+segments+are+encoded+differently，所以你也要小心。|245659|245660|正如您所看到的，每种方法都有优缺点。选择通常由你的客户决定。如果您提供的是FORM-based超文本标记语言页面，则使用@FormParam。如果您的客户机是基于JavaScript%2BHTML5的，那么您可能希望使用基于JAXB的序列化和JSON对象。MessageBodyReader/Writer实现应该为您处理必要的转义，这样就减少了出错的可能性。如果你的客户端是基于Java的，但是没有好的XML处理器(例如Android)，那么我可能会使用FORM编码，因为内容主体比URL更容易生成和编码。希望这个迷你wiki条目能够揭示JAX-RS支持的各种方法。|245661|注：为了充分披露信息，我还没有真正使用过Jersey的这个特性。我们正在修补它，因为我们已经部署了许多JAXB%2BJAX-RS应用程序，并且正在进入移动客户端领域。在HTML5或基于jQuery的解决方案中，JSON比XML更适合。|245662|entityMap|0|LINK|mutability|MUTABLE|url|https://jersey.github.io/documentation/latest/media.html#json|1|https://docs.oracle.com/javaee/7/api/javax/ws/rs/ext/MessageBodyReader.html|2|https://docs.oracle.com/javaee/7/api/javax/ws/rs/ext/MessageBodyWriter.html|3|https://docs.oracle.com/javaee/7/api/javax/ws/rs/FormParam.html|4|http://www.w3.org/TR/html4/interact/forms.html#h-17.13.4.1|5|https://docs.oracle.com/javaee/7/api/javax/ws/rs/HeaderParam.html|6|https://docs.oracle.com/javaee/7/api/javax/ws/rs/QueryParam.html|7|https://www.rfc-editor.org/rfc/rfc3986#section-3.4|8|https://docs.oracle.com/javaee/7/api/javax/ws/rs/Path.html|9|https://docs.oracle.com/javaee/7/api/javax/ws/rs/PathParam.html|10|https://www.rfc-editor.org/rfc/rfc3986#section-3.3^0|2|5|1J|R|0|0|0|5|5|0|0|1T|5|0|0|2B|H|1|2T|H|2|0|0|0|6|7|7|0|6|0|7|A|3|0|0|6|Z|4|0|0|0|0|0|0|0|8|0|L|C|5|0|0|0|0|0|0|0|8|0|W|B|6|0|0|0|0|G|N|7|0|0|0|8|0|29|5|8|2K|A|9|0|0|0|0|S|11|A|0|0|11|4|1O|A|3I|O|69|4|0|0|2|0^^$0|@$1|2|3|4|5|6|7|3C|8|@$9|3D|A|3E|B|C]]|D|@$9|3F|A|3G|1|3H]]|E|$]]|$1|F|3|G|5|H|7|3I|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|3J|8|@$9|3K|A|3L|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|3M|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|3N|8|@$9|3O|A|3P|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|H|7|3Q|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|3R|8|@]|D|@$9|3S|A|3T|1|3U]|$9|3V|A|3W|1|3X]]|E|$]]|$1|U|3|-4|5|6|7|3Y|8|@]|D|@]|E|$]]|$1|V|3|W|5|6|7|3Z|8|@$9|40|A|41|B|X]|$9|42|A|43|B|X]|$9|44|A|45|B|C]]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|46|8|@]|D|@$9|47|A|48|1|49]]|E|$]]|$1|10|3|11|5|H|7|4A|8|@]|D|@]|E|$I|J]]|$1|12|3|13|5|6|7|4B|8|@]|D|@$9|4C|A|4D|1|4E]]|E|$]]|$1|14|3|15|5|H|7|4F|8|@]|D|@]|E|$I|J]]|$1|16|3|17|5|6|7|4G|8|@]|D|@]|E|$]]|$1|18|3|19|5|6|7|4H|8|@]|D|@]|E|$]]|$1|1A|3|1B|5|H|7|4I|8|@]|D|@]|E|$I|J]]|$1|1C|3|-4|5|6|7|4J|8|@]|D|@]|E|$]]|$1|1D|3|1E|5|6|7|4K|8|@$9|4L|A|4M|B|X]]|D|@]|E|$]]|$1|1F|3|1G|5|6|7|4N|8|@]|D|@$9|4O|A|4P|1|4Q]]|E|$]]|$1|1H|3|1I|5|H|7|4R|8|@]|D|@]|E|$I|J]]|$1|1J|3|1K|5|6|7|4S|8|@]|D|@]|E|$]]|$1|1L|3|1M|5|H|7|4T|8|@]|D|@]|E|$I|J]]|$1|1N|3|1O|5|6|7|4U|8|@]|D|@]|E|$]]|$1|1P|3|-4|5|6|7|4V|8|@]|D|@]|E|$]]|$1|1Q|3|1R|5|6|7|4W|8|@$9|4X|A|4Y|B|X]]|D|@]|E|$]]|$1|1S|3|1T|5|6|7|4Z|8|@]|D|@$9|50|A|51|1|52]]|E|$]]|$1|1U|3|1V|5|H|7|53|8|@]|D|@]|E|$I|J]]|$1|1W|3|1X|5|6|7|54|8|@]|D|@]|E|$]]|$1|1Y|3|1Z|5|H|7|55|8|@]|D|@]|E|$I|J]]|$1|20|3|21|5|6|7|56|8|@]|D|@$9|57|A|58|1|59]]|E|$]]|$1|22|3|-4|5|6|7|5A|8|@]|D|@]|E|$]]|$1|23|3|24|5|6|7|5B|8|@$9|5C|A|5D|B|X]]|D|@]|E|$]]|$1|25|3|26|5|6|7|5E|8|@]|D|@$9|5F|A|5G|1|5H]|$9|5I|A|5J|1|5K]]|E|$]]|$1|27|3|28|5|H|7|5L|8|@]|D|@]|E|$I|J]]|$1|29|3|2A|5|6|7|5M|8|@]|D|@]|E|$]]|$1|2B|3|2C|5|H|7|5N|8|@]|D|@]|E|$I|J]]|$1|2D|3|2E|5|6|7|5O|8|@]|D|@$9|5P|A|5Q|1|5R]]|E|$]]|$1|2F|3|-4|5|6|7|5S|8|@]|D|@]|E|$]]|$1|2G|3|2H|5|6|7|5T|8|@$9|5U|A|5V|B|C]|$9|5W|A|5X|B|C]|$9|5Y|A|5Z|B|C]|$9|60|A|61|B|C]]|D|@]|E|$]]|$1|2I|3|2J|5|6|7|62|8|@$9|63|A|64|B|X]]|D|@]|E|$]]|$1|2K|3|-4|5|6|7|65|8|@]|D|@]|E|$]]]|2L|$2M|$5|2N|2O|2P|E|$2Q|2R]]|2S|$5|2N|2O|2P|E|$2Q|2T]]|2U|$5|2N|2O|2P|E|$2Q|2V]]|2W|$5|2N|2O|2P|E|$2Q|2X]]|2Y|$5|2N|2O|2P|E|$2Q|2Z]]|30|$5|2N|2O|2P|E|$2Q|31]]|32|$5|2N|2O|2P|E|$2Q|33]]|34|$5|2N|2O|2P|E|$2Q|35]]|36|$5|2N|2O|2P|E|$2Q|37]]|38|$5|2N|2O|2P|E|$2Q|39]]|3A|$5|2N|2O|2P|E|$2Q|3B]]]]

Your <code>@POST</code> method should be accepting a JSON object instead of a string. Jersey uses JAXB to support marshaling and unmarshaling JSON objects (see <a href="https://jersey.github.io/documentation/latest/media.html#json" rel="nofollow noreferrer">the jersey docs for details</a>). Create a class like:
<pre><code>@XmlRootElement
public class MyJaxBean {
 @XmlElement public String param1;
 @XmlElement public String param2;
}
</code></pre>
Then your <code>@POST</code> method would look like the following:
<pre><code>@POST @Consumes(&quot;application/json&quot;)
@Path(&quot;/create&quot;)
public void create(final MyJaxBean input) {
 System.out.println(&quot;param1 = &quot; + input.param1);
 System.out.println(&quot;param2 = &quot; + input.param2);
}
</code></pre>
This method expects to receive JSON object as the body of the HTTP POST. JAX-RS passes the content body of the HTTP message as an unannotated parameter -- <code>input</code> in this case. The actual message would look something like:
<pre><code>POST /create HTTP/1.1
Content-Type: application/json
Content-Length: 35
Host: www.example.com

{&quot;param1&quot;:&quot;hello&quot;,&quot;param2&quot;:&quot;world&quot;}
</code></pre>
Using JSON in this way is quite common for obvious reasons. However, if you are generating or consuming it in something other than JavaScript, then you do have to be careful to properly escape the data. In JAX-RS, you would use a <a href="https://docs.oracle.com/javaee/7/api/javax/ws/rs/ext/MessageBodyReader.html" rel="nofollow noreferrer">MessageBodyReader</a> and <a href="https://docs.oracle.com/javaee/7/api/javax/ws/rs/ext/MessageBodyWriter.html" rel="nofollow noreferrer">MessageBodyWriter</a> to implement this. I believe that Jersey already has implementations for the required types (e.g., Java primitives and JAXB wrapped classes) as well as for JSON. JAX-RS supports a number of other methods for passing data. These don't require the creation of a new class since the data is passed using simple argument passing.
<hr />
HTML <code>&lt;FORM&gt;</code>
The parameters would be annotated using <a href="https://docs.oracle.com/javaee/7/api/javax/ws/rs/FormParam.html" rel="nofollow noreferrer">@FormParam</a>:
<pre><code>@POST
@Path(&quot;/create&quot;)
public void create(@FormParam(&quot;param1&quot;) String param1,
 @FormParam(&quot;param2&quot;) String param2) {
 ...
}
</code></pre>
The browser will encode the form using <a href="http://www.w3.org/TR/html4/interact/forms.html#h-17.13.4.1" rel="nofollow noreferrer">&quot;application/x-www-form-urlencoded&quot;</a>. The JAX-RS runtime will take care of decoding the body and passing it to the method. Here's what you should see on the wire:
<pre><code>POST /create HTTP/1.1
Host: www.example.com
Content-Type: application/x-www-form-urlencoded;charset=UTF-8
Content-Length: 25

param1=hello&amp;param2=world
</code></pre>
The content is <a href="https://www.rfc-editor.org/rfc/rfc3986#section-2.1" rel="nofollow noreferrer">URL encoded</a> in this case.
If you do not know the names of the FormParam's you can do the following:
<pre><code>@POST @Consumes(&quot;application/x-www-form-urlencoded&quot;)
@Path(&quot;/create&quot;)
public void create(final MultivaluedMap&lt;String, String&gt; formParams) {
 ...
}
</code></pre>
<hr />
HTTP Headers
You can using the <a href="https://docs.oracle.com/javaee/7/api/javax/ws/rs/HeaderParam.html" rel="nofollow noreferrer">@HeaderParam</a> annotation if you want to pass parameters via HTTP headers:
<pre><code>@POST
@Path(&quot;/create&quot;)
public void create(@HeaderParam(&quot;param1&quot;) String param1,
 @HeaderParam(&quot;param2&quot;) String param2) {
 ...
}
</code></pre>
Here's what the HTTP message would look like. Note that this POST does not have a body.
<pre><code>POST /create HTTP/1.1
Content-Length: 0
Host: www.example.com
param1: hello
param2: world
</code></pre>
I wouldn't use this method for generalized parameter passing. It is really handy if you need to access the value of a particular HTTP header though.
<hr />
HTTP Query Parameters
This method is primarily used with HTTP GETs but it is equally applicable to POSTs. It uses the <a href="https://docs.oracle.com/javaee/7/api/javax/ws/rs/QueryParam.html" rel="nofollow noreferrer">@QueryParam</a> annotation.
<pre><code>@POST
@Path(&quot;/create&quot;)
public void create(@QueryParam(&quot;param1&quot;) String param1,
 @QueryParam(&quot;param2&quot;) String param2) {
 ...
}
</code></pre>
Like the previous technique, passing parameters via the query string does not require a message body. Here's the HTTP message:
<pre><code>POST /create?param1=hello&amp;param2=world HTTP/1.1
Content-Length: 0
Host: www.example.com
</code></pre>
You do have to be particularly careful to properly <a href="https://www.rfc-editor.org/rfc/rfc3986#section-3.4" rel="nofollow noreferrer">encode query parameters</a> on the client side. Using query parameters can be problematic due to URL length restrictions enforced by some proxies as well as problems associated with encoding them.
<hr />
HTTP Path Parameters
Path parameters are similar to query parameters except that they are embedded in the HTTP resource path. This method seems to be in favor today. There are impacts with respect to HTTP caching since the path is what really defines the HTTP resource. The code looks a little different than the others since the <a href="https://docs.oracle.com/javaee/7/api/javax/ws/rs/Path.html" rel="nofollow noreferrer">@Path</a> annotation is modified and it uses <a href="https://docs.oracle.com/javaee/7/api/javax/ws/rs/PathParam.html" rel="nofollow noreferrer">@PathParam</a>:
<pre><code>@POST
@Path(&quot;/create/{param1}/{param2}&quot;)
public void create(@PathParam(&quot;param1&quot;) String param1,
 @PathParam(&quot;param2&quot;) String param2) {
 ...
}
</code></pre>
The message is similar to the query parameter version except that the names of the parameters are not included anywhere in the message.
<pre><code>POST /create/hello/world HTTP/1.1
Content-Length: 0
Host: www.example.com
</code></pre>
This method shares the same encoding woes that the query parameter version. <a href="https://www.rfc-editor.org/rfc/rfc3986#section-3.3" rel="nofollow noreferrer">Path segments are encoded differently</a> so you do have to be careful there as well.
<hr />
As you can see, there are pros and cons to each method. The choice is usually decided by your clients. If you are serving <code>FORM</code>-based HTML pages, then use <code>@FormParam</code>. If your clients are JavaScript+HTML5-based, then you will probably want to use JAXB-based serialization and JSON objects. The <code>MessageBodyReader/Writer</code> implementations should take care of the necessary escaping for you so that is one fewer thing that can go wrong. If your client is Java based but does not have a good XML processor (e.g., Android), then I would probably use <code>FORM</code> encoding since a content body is easier to generate and encode properly than URLs are. Hopefully this mini-wiki entry sheds some light on the various methods that JAX-RS supports.
Note: in the interest of full disclosure, I haven't actually used this feature of Jersey yet. We were tinkering with it since we have a number of JAXB+JAX-RS applications deployed and are moving into the mobile client space. JSON is a much better fit that XML on HTML5 or jQuery-based solutions.

My POST method looks like this:

<pre><code>@POST
@Consumes({"application/json"})
@Path("create/")
public void create(String param1, String param2){
 System.out.println("param1 = " + param1);
 System.out.println("param2 = " + param2);
}
</code></pre>

When I create a Jersey Client in Netbeans the method who calls the post method looks like this:

<pre><code>public void create(Object requestEntity){
 webResource.path("create").type(MediaType.APPLICATION_JSON).post(requestEntity);
}
</code></pre>

When running this test:

<pre><code>@Test
public void hello(){
 String json = "{param1=\"hello\",param2=\"hello2\"}";
 this.client.create(json);
}
</code></pre>

It gives the following output in the server:

<pre><code>INFO: param1 = {param1="hello",param2="hello2"}
INFO: param2 = 
</code></pre>

What do I need to change so that the parameters are giving the correct value?

How to access parameters in a RESTful POST method

我的POST方法看起来像这样：@POST@Consumes({"application/json"})@Path("create/")public void create(String param1, String param2){    System.out.println("param1 = " + param1)...

问如何访问RESTful POST方法中的参数
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何访问RESTful POST方法中的参数EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何访问RESTful POST方法中的参数
EN