HTTP request and response mapping in Gloop
Endpoints invoke services based on certain configured conditions and when they do invoke a service, TORO Integrate tries to inject as much useful data as it can about the endpoint and what triggered the service, so that this data may be used during the execution of the service. TORO Integrate will map data to the service (in the form of method arguments) if its method parameters have types and names that match any of the entries in the list of supported or injectable endpoint service arguments1.
The same can be said for how TORO Integrate maps HTTP request related data to the inputs of a Gloop service. The only difference is that the names of the parameters will change, to coincide with things such as:
- Request headers
- HTTP request parameters
- HTTP request path tokens (URI variables)
As a result, we think it's important for you to understand how HTTP data mapping works in Gloop so you could write cleaner code, and allow TORO Integrate to do all the heavy lifting for you.
Gloop object converters
Gloop has the ability to convert objects from one type to another for you. These converters are also used by Gloop when mapping request data to the input properties of a Gloop service.
Endpoint types vary in which service arguments they support. To learn which parameters are supported by a type, please visit the respective endpoint type's documentation page. ↩