Checks the presence of the named Api Key parameter.
Allows binding of a value to an entity (eg.
Represents the binding of a parameter to it's value in a particular context
Spec required to marshall a body of a custom type
Mechanism to extract (or fail to extract) an entity value from a particular 'From' context
Mechanism to extract (or fail to extract) a parameter from a particular 'From' context, adding
Represents a object which was provided and extracted successfully
Result of an attempt to extract an object from a target
Represents a object which could not be extracted due to it being invalid or missing when required
The body entity of a encoded HTML form.
Forms are effectively modelled as a collection of fields.
Support for parameters which can have more than one value (e.
For optional Parameters, adds the ability to bind an Optional value as well as a concrete value
How a parameter is represented in the HTTP message (JSON type)
A parameter is a name-value pair which can be encoded into an HTTP message.
Parameter location specific utility functions to assist with extraction and binding of values
Spec required to marshall and demarshall a parameter of a custom type
By implementing ParameterSpecSupplier[T], we can declare parameters using a shorthand: eg.
Prototype functions for creating parameters of various types.
Used to transparently copy the value out of an incoming request (or form etc.
Represents the ability to retrieve a value from an enclosing object (request/form etc.
Endpoint security.
Represents a single entity which makes up the entirety of an HTTP message body.
Factory methods for various supported HTTP body types.
Parameters which are bound to request/response headers
Default NoOp security filter.
Represents an optional object which was not provided - this is still a non-failing case
Predefined ParameterSpec instances for common types
Parameters which are bound to the path segments of a URL
Parameters which are bound to the query part of a URL