All Classes and Interfaces

Class
Description
 
A bespoken MessageProducer implementation designed to provide always consistent semantics when sending messages to Vertx' EventBus.
 
A listener for "Configuration Loaded" event.
 
Automatically replies to async events received from EventBus.
Automatically configures Vert.x components managed by Kos.
 
 
 
A predicate-based Validation.
A Validation that assume all objects are valid.
 
 
Bridges the communication between the local EventBus with a remote broker (e.g.
 
Represents the outcome of an attempt to initialise either EventSubscriptionSink or EventPublisherSink.
 
 
 
Handles received events asynchronously.
 
Defines an EventBus publisher.
Defines how to listen message from externally managed brokers (e.g.
Versatile exception handler abstraction.
 
 
Loads implementations.
Customized optional result.
 
 
This object is read-only representation of all sensible configuration that have been previously defined at the Kos' application initialization.
 
 
Convenient Exception class.
Utility methods internally used by Kos.
Convenient HashMap builder.
Simplified launcher wrapping Vert.x deployment of Verticles.
 
Defines how Kos will handle the serialization and deserialization for every received request.
Allows external plugins to configures Kos.
 
The default Exception Handler mechanism.
 
 
Methods to read and parse data from the incoming request.
 
 
 
 
 
Represents a (mutable object) response to be sent to the http client.
 
 
 
 
Small layer that wraps Router aiming to simplify a few common aspects regarding route configuration, like intercepting requests and the reading body requests in a POST, PUT and PATCH requests.
 
Abstracts how kos can convert strings (like Headers and query parameters) into objects.
Default implementation of StringConverter.
 
A validation rule for the given type.
 
 
Automatically configures the DefaultValidation and memorises all found validations in the class path.
 
 
 
Abstracts the creation of a Vert.x web server, automating a few repetitive tasks, automatically loading routes if available, and avoiding common mistakes made during the application bootstrap.
 
 
 
Called by VertxWebServer, implementations of this interface will have the opportunity to enhance or change the web server configuration before it is started.
Data available before deploy the web server.