All Classes and Interfaces
Class
Description
The AclAction secures an API by making sure that a requests matches one or
more declared AclRules
Actions perform some work when matched to a Request and potentially contribute to the content of the Response.
Contains the Servers, Dbs, Collections, Endpoints and Actions that make up a REST API.
Listener that can be registered with an
Api to receive lifecycle,
per request and per error callback notifications.Represents a REST Collection and maps JSON properties property names and logical cross Collection data relationships to underlying Db tables and column names.
An adapter to an underlying data source.
A single Endpoint, bundling one or more Path match relative Actions, is selected to service a Request.
Matches inbound Request Url paths to an Api Endpoint and executes associated Actions.
Receives
Engine and Api lifecycle,
per request and per error callback notifications.page(pageNum, [pageSize])
pageNum(pageNum, [pageSize])
offset(offset, [limit])
limit(limit, [offset])
pageSize(pageSize)
Query<T extends Query,D extends Db,S extends Select,F extends From,W extends Where,R extends Group,O extends Order,G extends Page>
Represents a full RQL query with a SELECT,WHERE,GROUP,ORDER, and PAGE clause.
This class serves as holder for the Response returned from a RestClient call AND as the object
used to construct your own response to an Engine request.
Results are returned by a Db and transformed by Actions into Response content.
Matches against an HTTP method and URL path to determine if the object
should be included when processing the associated Request.
Static constants for HTTP status codes.
Implemented by different runtimes, for example a servlet vs a lambda, to enable different file upload mechanisms.
Utility class for parsing and working with HTTP(S) URLs.
Utility designed to make it easy to validate request properties or request body
json values while you are retrieving them.