Package-level declarations

One setting a provider (a store's, a dataset backend's) reads from its configuration, as it declares it: its key, what it means (description, the configuration reference's text), the type of its value and its default (null when it has none), and where it may be set (scope). A provider lists every option it reads, and reads each through it, so the host binds, checks and documents exactly those: an option of Scope.TYPE is set for every instance of the provider's type under wow.<type>.<key>, and each instance may set it over that; a key a provider does not declare fails the start, naming the declared ones.

A configuration Wow cannot start with: key is the configuration key at fault, value its value as configured (null when it is not set, or when the fault is between keys), reason what is wrong and fix what to change. The core modules that enforce a rule of the configuration throw it where the rule lives (the internal port's security floor of wow-http, the query bulkheads of wow-query), and a host reports it as it reports its own: the Spring Boot host through a failure analyzer, instead of a stack of bean creation failures.

Throws a WowConfigurationException of key with value and fix when condition is false.

value, or, when it is null, a WowConfigurationException of key with fix; configured is the key's value, null when it is not set.