Comparison between @QueryParam and @pathparam

Source: http://jackyrong.iteye.com/blog/1128364

1 See @queryparam first.

2. Path ("/users")
4. public class UserService {
8. @GET
10. @Path ("/query")
12. Public Response Getusers (
14. @QueryParam ("from") int from,
16. @QueryParam ("to") int to,
18. @QueryParam ("list<string>") {
22. Return Response
24. . Status (200)
26. . Entity ("Getusers is called, from: ' + from + ', to: ' + to
28. + ", by" + orderby.tostring ()). build ();
32. }
36. }

URL input is: users/query?from=100&to=200&orderby=age&orderby=name
At this point, the output is:
Getusers is called, from:100, to:200, Orderby[age, name]

Note that, unlike @pathparam, @queryparam specifies that the parameters in the URL appear as key-value pairs, while in the program
The @QueryParam ("from") int from is the value of the from in the URL, whereas in @pathparem, only the value of the parameter appears in the URL, no key-value pairs, such as "/users/2011/06/30"

2, @PathParam example

2. @GET
4. @Path ("{year}/{month}/{day}")
6. Public Response Getuserhistory (
8. @PathParam ("year") int of year,
10. @PathParam ("month") int month,
12. @PathParam ("day") int day) {
16. String date = year + "/" + month + "/" + day;
20. Return Response.Status (200)
22. . Entity ("Getuserhistory is called, Year/month/day:" + date)
24. . build ();
28. }

Comparison between @QueryParam and @pathparam