Page History
...
Multiexcerpt | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Each REST port type should have a <<RESTError>> class assigned. The Bridge will use this class as output in case of error (see Defining a REST Service Interface). In the support manager example, REST port type SupportAPI has class RESTError assigned as error class. Using function
Assign the error object and a HTTP status code that corresponds to the error. This information will be returned via the HTTP response.
In the support manager example, if user does not provide a support case id with the REST call, the implementation is as follows: Error Handling for Specific Error ClassesIf you defined a specific error class or Blob (Bridge 7.1.0) for a specific HTTP status code as described on Defining a REST Service Interface, you can use the same way as described above to provide the error details to the response. Provide the error details to an instance of the specific error class or Blob and provide the error class to the response object. |
...
- Output: There can be no or exactly one output parameter via the response body. It has to be of complex type or of type Blob (Bridge 7.1.0). More output parameters can be specified via the HTTP headers.
...
The REST method can provide multiple output parameters via the response headers. These parameters can be of simple type or array of simple type.
Info |
---|
As of Runtime 2019.1,we changed how the Runtime handles header parameters that are not set. If you do not set a header parameter that is defined for an operation, this parameter is omitted and not provided in the response headers. |
...