JBoss resteasy 2 URL matching

In the previous article helloworld, I briefly introduced the entry point. This article describes its URL matching, which is also a rest
An important part
Example:

Java code

1. @ Path ("/users ")
2. Public class userrestservice {
4. @ Get
5. @ Path ("{name }")
6. Public Response getuserbyname (@ pathparam ("name") string name ){
8. Return response. Status (200)
9. . Entity ("getuserbyname is called, name:" + name). Build ();
11. }
12. @ Get
13. @ Path ("{ID: \ D +}") // support digit only
    
14. Public Response getuserbyid (@ pathparam ("ID") string ID ){
16. Return response. Status (200). Entity ("getuserbyid is called, ID:" + id). Build ();
18. }
20. @ Get
21. @ Path ("/username/{Username: [A-Za-Z] [a-zA-Z_0-9]}")
22. Public Response getuserbyusername (@ pathparam ("username") string username ){
24. Return response. Status (200)
25. . Entity ("getuserbyusername is called, Username:" + username). Build ();
27. }
29. @ Get
30. @ Path ("/books/{ISBN: \ D + }")
31. Public Response getuserbookbyisbn (@ pathparam ("ISBN") string ISBN ){
33. Return response. Status (200)
34. . Entity ("getuserbookbyisbn is called, ISBN:" + ISBN). Build ();
36. }

@Path("/users")public class UserRestService { @GET@Path("{name}")public Response getUserByName(@PathParam("name") String name) { return Response.status(200).entity("getUserByName is called, name : " + name).build(); }@GET@Path("{id : \\d+}") //support digit onlypublic Response getUserById(@PathParam("id") String id) {    return Response.status(200).entity("getUserById is called, id : " + id).build(); } @GET@Path("/username/{username : [a-zA-Z][a-zA-Z_0-9]}")public Response getUserByUserName(@PathParam("username") String username) {    return Response.status(200).entity("getUserByUserName is called, username : " + username).build(); } @GET@Path("/books/{isbn : \\d+}")public Response getUserBookByISBN(@PathParam("isbn") String isbn) {    return Response.status(200).entity("getUserBookByISBN is called, isbn : " + isbn).build(); }

We can see that regular expressions are also supported. Therefore, it is easy to see:

1) "/users/999"
Return Value: getuserbyid is called, ID: 999

2)/users/username/AAA"
Mismatch

3) users/books/999"
Return Value: getuserbookbyisbn is called, ISBN: 999

Let's look at the example:
 

Java code

1. @ Path ("/users ")
2. Public class userrestservice {
4. @ Get
5. @ Path ("{ID }")
6. Public Response getuserbyid (@ pathparam ("ID") string ID ){
8. Return response. Status (200). Entity ("getuserbyid is called, ID:" + id). Build ();
10. }

@Path("/users")public class UserRestService { @GET@Path("{id}")public Response getUserById(@PathParam("id") String id) {    return Response.status(200).entity("getUserById is called, id : " + id).build(); } 

Then "/users/22667788" matches
Getuserbyid is called, ID: 22667788

Example of multiple parameter input:
 

Java code

1. @ Path ("/users ")
2. Public class userrestservice {
4. @ Get
5. @ Path ("{year}/{month}/{day }")
6. Public Response getuserhistory (
7. @ Pathparam ("year") int year,
8. @ Pathparam ("month") int month,
9. @ Pathparam ("day") int day ){
11. String date = year + "/" + month + "/" + Day;
13. Return response. Status (200)
14. . Entity ("getuserhistory is called, year/month/day:" + date)
15. . Build ();
17. }

@Path("/users")public class UserRestService { @GET@Path("{year}/{month}/{day}")public Response getUserHistory(@PathParam("year") int year,@PathParam("month") int month, @PathParam("day") int day) {    String date = year + "/" + month + "/" + day;    return Response.status(200).entity("getUserHistory is called, year/month/day : " + date).build(); } 

Then:
"/Users/2011/06/30"
Output:
Getuserhistory is called, year/month/day: 2011/6/30