How to create POST, PUT and DELETE method in Grails application?

Question

I have a Grails 2.4.2 application that I want to communicate with another application, and this interaction should occur through a Rest service provided by Grails. Today as it is implemented just I inform . json at the end of the URL that it returns the formatted data. However I would like to know how to manipulate these implementations in order to add the methods POST, PUT and DELETE.

I did a search on official documentation, with that I arrived at the following encoding:

Urlmappings.groovy

class UrlMappings {

static mappings = {
    "/$controller/$action?/$id?(.$format)?"{
        constraints {
            // apply constraints here
        }
    }

    "/"(controller:"main")
    "500"(view:'/error')

    "/patrimonios"(resource:'Patrimonio')
    }
}

When I run the application and access the link http://localhost:8080/Patrimonio/patrimonios I got a blank page coming back. I tested the POST and DELETE methods through the POSTER addon and nothing happened either. Therefore, I would like to know how best to proceed to achieve the desired goal?

Urlmappings.groovy (EDITED)

class UrlMappings {

    static mappings = {
        "/$controller/$action?/$id?(.$format)?"{
            constraints {
                // apply constraints here
            }
        }

        "/"(controller:"main")
        "500"(view:'/error')

        "/api/patrimonio/"(controller: "PatrimonioController") {
            action = [GET: "get"]
        }

    }
}

Answer 1

Below is an example that I use in a Grails application (2.2.5) which is a REST service consumed by another application, also developed Grails (2.5.0).

In Urlmapping:

    "/api/client/$labcode/$cliCode"(controller: "client") {
        action = [GET: "get"]
    }

    "/api/client"(controller: "client") {
        action = [POST: "save", PUT:"update"]
    }

1st Urlmapping specifies that any HTTP request of the type GET that arrive to /api/client/$labcode/$cliCode will be redirected to the action "get" of the controller "client".

$labcode and $cleavage are parameters passed to the action.

Example of HTTP GET request that is captured by the 1st Mapping URL:

https://localhost:8443/Service/api/client/BRMIN01/CL-000223

in this context, the application is called Service. The rest is exactly in the pattern for capturing the Mapping URL.

The second Mapping specifies that any HTTP request of type POST to /api/client will be redirected to the action "save" of the controller "client". Already requisitions of the type PUT are directed to the action "update" of the same controller.

In the example of the question, one can do this:

"/$controller/$action?/$id?(.$format)?" {
    [POST: "save", PUT:"update", DELETE:"delete"]
    constraints {
        // apply constraints here
    }
 }

In this case, you are specifying that HTTP requests of type POST, PUT and DELETE that obey the mapping rule will be directed to save, update and delete actions, respectively.

On the blank pages, has been identified by chat that a non-existent ID was being passed into the database.