Package-level declarations
Types
How a route takes one identity fact.
Further request headers the HTTP adapter reads for the space and the request ID, after Wow's own Wow-Space-Id and Command-Request-Id, in order. An integration (CoSec, say) contributes its headers here once instead of overriding the command builder extractor and the query request scope. Since 9.3.0.
The identity of one request to one aggregate's route: each fact (tenant, owner, aggregate ID, space, request ID) read where the route states it, by the same rules as the built-in command and query handlers (see RouteIdentityBinding), header aliases included. A custom handler reads identity through it, with ServerRequest.identity.
The identity side of one materialized route: its declared identity path variables, the header aliases, and, for a route of one aggregate, that aggregate's RouteIdentityBinding, computed once. Carried to the handlers as a request attribute; a handler of another aggregate (the command facade) gets a binding computed from the same path variables.
Where one route takes each identity fact from, decided once from the route contract when the router is materialized: the path variables the contract declares, the aggregate's static tenant, ownership policy and space, and the header aliases. Each value is then decided by IdentityResolver, so the route, not each handler, states which source is authoritative:
Where a route takes one identity fact from.
Functions
The identity this request states for the aggregate of aggregateMetadata.
The identity this request states for the aggregate of aggregateRouteMetadata.