The XDATA UrlMap associates the REST call with the method that implements the service. It can either directly send the call to a method based on the contents of the URL or it can forward the call to another subclass of %CSP.REST
based on the URL. If the web application is handling a small number of related services, you can send the call directly to the method that implements it. However, if the web application is handling a large number of disparate services, you can define separate subclasses of %CSP.REST
, each of which handles a set of related services. Then the subclass of %CSP.REST
that handles the web application simply forwards the REST call to the appropriate subclass.
If the subclass of %CSP.REST
is sending the call directly to the methods, the URLMap contains a Routes definition that contains a series of Route elements. Each Route specifies a class method to be called for the specified URL and HTTP operation. Typically REST uses the GET, POST, PUT, or DELETE operations, but you can specify any HTTP operation. The URL can optionally include parameters that are specified as part of the REST URL and passed to the specified method as parameters.
If the subclass of %CSP.REST
is forwarding the calls to other subclasses of %CSP.REST
, the UrlMap contains a Routes definition that contains a series of Map elements. The Map statement forwards all calls with the specified prefix to its associated %CSP.REST
subclass, which will then implement the behavior. It can implement the behavior by sending the call directly to a method or by forwarding it to another subclass.
Caché compares the incoming REST URL with the Route URL property or the Map Prefix property. It starts at the first Route or Map element and continues to test each following element until it finds a match. Once it finds a match it either sends the incoming call to the call specified in the Route or forwards the URL to the class specified in the Map. In both cases, it ignores any elements in the Routes after the matching element; consequently, the order of the elements in the Routes is significant. If an incoming URL could match multiple elements of the Routes, Caché uses the first matching element and ignores any subsequent possible matches.
Caché compares the incoming URL and the HTTP request method to each Route element in Routes. It calls the method specified in the first matching Route element. The Route element has three parts:
For example, the DocServer sample defines the following Route:
<Route Url="/echo" Method="POST" Call="Echo" Cors="false" />
The complete REST URL consists of the following pieces:
For the preceding example, the complete REST call as shown by a TCP tracing utility is:
POST /csp/samples/docserver/echo HTTP/1.1
The following Route definition defines two parameters, namespace and class, in the URL:
<Route Url="/class/:namespace/:classname" Method="GET" Call="GetClass" />
A REST call URL starts with /csp/samples/docserver/class/
and the next two elements of the URL specify the two parameters. The GetClass method uses these parameters as the namespace and the class name that you are querying. For example, the REST call:
calls the GetClass method and specifies samples and Cinema.Review as the parameter values. The definition of the GetClass method starts with:
/// This method returns the class text for the named cache class
pNamespace As %String,
pClassname As %String) As %Status
You can define a different method for each HTTP request method for a single URL. For example, you could define the following:
<Route Url="/request" Method="GET" Call="GetRequest" />
<Route Url="/request" Method="POST" Call="PostRequest" />
With these routes, if the URL /csp/samples/docserver/request
is called with an HTTP GET method, the GetRequest() method is invoked. If it is called with an HTTP POST method, the PostRequest() method is invoked. In the DocServer sample, both HTTP request methods are handled by a single Call method. The Route definitions in the sample is
<Route Url="/request" Method="GET" Call="Request" />
<Route Url="/request" Method="POST" Call="Request" />
In this case, the Request() method handles the call for either a GET or a POST operation. If this method needs to distinguish between a GET and a POST operation, it can do this by examining the CSP request object, which contains the text of the URL.
If you want to separate the code implementing the REST services from the %CSP.REST
dispatch code, you can define the methods implementing the REST services in another class and specify the class and method in the Call element.
Regular Expressions in the Route Map
You can use regular expressions within the route map. InterSystems suggests that you do so only if there is no other way to define the REST service to meet your needs. This section provides the details. (For information on regular expressions in ObjectScript, see Regular Expressions
in Using ObjectScript
Internally, the :parameter-name
syntax for defining parameters in the URL is implemented using regular expressions. Each segment specified as :parameter-name
is converted to a regular expression that contains a repeating matching group
, specifically to the ([^/]+)
regular expression. This syntax matches any string (of non-zero length), as long as that string does not include the /
(slash) character. So the GetClass()
sample, which is Url="/class/:namespace/:classname"
, is equivalent to:
<Route Url="/class/([^/]+)/([^/]+)" Method="GET" Call="GetClass" />
where there are two matching groups that specify two parameters.
In most cases this format provides enough flexibility to specify the REST URL, but advanced users can use the regular expression format directly in the route definition. The URL must match the regular expression, and each matching group, which is specified by a pair of parentheses, defines a parameter to be passed to the method.
For example, consider the following route map:
<Route Url="/Move/:direction" Method="GET" Call="Move" />
<Route Url="/Move2/(east|west|north|south)" Method="GET" Call="Move" />
For the first route, the parameter can have any value. No matter what value the parameter has, the Move()
method is called. For the second route, the parameter must be one of east west north
; if you call the second route with a parameter value other than those, the Move()
method is not called, and REST service returns a 404 error because the resource cannot be found.
This simple example is meant only to demonstrate the difference between the usual parameter syntax and a regular expression. In the case discussed here, there is no need for a regular expression because the Move()
method can (and should) check the value of the parameter and respond appropriately. In the following cases, however, a regular expression is helpful:
Caché compares the incoming URL to the prefix in each Map element in Routes. It forwards the incoming REST call to the %CSP.REST
subclass specified in the first matching Map element. That class processes the remainder of the URL, typically calling the method that implements the service. The Map element has two parts:
Consider the following URLMap that contains three Map elements.
<Map Prefix="/coffee/sales" Forward="MyLib.coffee.SalesREST"/>
<Map Prefix="/coffee/repairs" Forward="MyLib.coffee.RepairsREST"/>
<Map Prefix="/coffee" Forward="MyLib.coffee.MiscREST"/>
The complete REST URL to call one of these REST services consists of the following pieces:
For example, the following REST call:
matches the first map with the Prefix /coffee/sales
and forwards the REST call to the MyLib.coffee.SalesREST
class. That class will look for a match for the remainder of the URL, "/reports/id/875".
As another example, the following REST call:
matches the third map with the Prefix /coffee
and forwards the REST call to the MyLib.coffee.MiscREST
class. That class will look for a match for the remainder of the URL, "/inventory/machinetype/drip".
In this URLMap example, if the Map with the Prefix="/coffee" was the first map, all REST calls with /coffee would be forwarded to the MyLib.coffee.MiscREST
class even if they matched one of the following Map elements. The order of the Map elements in Routes is significant.
© 1997-2019 InterSystems Corporation, Cambridge, MA