Package-level declarations
Types
The caller scope of the dataset routes: the host's identity scope followed by every ScopeContributor's dataset dimension, each half appended to the same half, as me.ahoo.wow.webflux.route.query.CompositeQueryRequestScope does for the aggregate routes. Since 9.9.0.
One dataset of the directory: its name, its title, and the version of its capability descriptor, null while its schema cannot be compiled (its table does not match its declaration, say), which the dataset's own schema route explains.
GET /dataset: the datasets this instance serves, by name, as of the request (dataset platform design §4.4). Who may see the directory, and each dataset, is the gateway's path rules' to decide; the directory adds no access model.
Creates the handler of the dataset directory route, identified by handlerKey.
One dataset query route: it finds the dataset named by {context} and {dataset} (404 when this instance serves no such dataset) and runs operation through the same pipeline as an aggregate's query routes: the HTTP entry, the caller scope, the HTTP guard and the capability descriptor's ETag.
Creates the handler of one dataset route, identified by handlerKey.
The query operations a dataset route serves.
The caller scope of a dataset route, mapped by admission onto the dataset's own tenant, owner and space columns. Only an authenticated part is a security boundary.
Reads the tenant from the {tenantId} path variable, else Command-Tenant-Id; the owner from Command-Owner-Id and the space from Wow-Space-Id, each only when the dataset has that column. Every value comes from the request, so each is declared; override provenance when a trusted component (an authenticating gateway that owns these headers, say) vouches for them.