All Classes and Interfaces

Class	Description
AbstractCommandBus	Base implementation of the CommandBus - provides default implementation for all operations except for CommandBus.sendAndDontWait(Object)/CommandBus.sendAndDontWait(Object, Duration)
AnnotatedCommandHandler	Extending this class will allow you to colocate multiple related Command handling methods inside the same class and use it together with the LocalCommandBus Each method must accept a single Command argument, may return a value or return void and be annotated with either the Handler or CmdHandler annotation. The method argument type is matched against the concrete command type using Class.isAssignableFrom(Class). The method accessibility can be any combination of private, protected, public, etc. Example:
AnnotatedEventHandler	Extending this class will allow you to colocate multiple related Event handling methods inside the same class and use it together with the LocalEventBus Each method must accept a single Event argument, return void and be annotated with the Handler annotation. The method argument type is matched against the concrete event type using Class.isAssignableFrom(Class). The method accessibility can be any combination of private, protected, public, etc. Example:
AsyncEventHandler	Annotate an EventHandler/AnnotatedEventHandler with this annotation to have the EventHandler be registered as an asynchronous event-handler with the default LocalEventBus (default is registering them as a synchronous event handler).
CmdHandler	AnnotatedCommandHandler specific method annotation, that can be used instead of Handler, that can be applied to any single argument method inside a AnnotatedCommandHandler The annotated methods can have the following accessibility: private, protected, public, etc.
CommandBus	The CommandBus provides an indirection between a command and the CommandHandler that's capable of handling the command. Commands can be sent synchronously using CommandBus.send(Object) or asynchronously using CommandBus.sendAsync(Object) that returns a Mono. The handling of a command usually doesn't return any value (according to the principles of CQRS), however the LocalCommandBus API allows a CommandHandler to return a value if needed (e.g. such as a server generated id) One important rule is that there can only be one CommandHandler instance that can handle any given command type. If multiple CommandHandler claim that they all can handle a given command type then CommandBus.send(Object)/CommandBus.sendAsync(Object) will throw MultipleCommandHandlersFoundException If no CommandHandler's can handle the given command type then CommandBus.send(Object)/CommandBus.sendAsync(Object) will throw NoCommandHandlerFoundException
CommandBusInterceptor	An CommandBusInterceptor allows you to intercept Commands before and after they're being handled by the LocalCommandBus
CommandBusInterceptorChain	Generic interceptor chain concept that supports intercepting LocalCommandBus operations
CommandBusInterceptorChain.DefaultCommandBusInterceptorChain	Default implementation for the CommandBusInterceptorChain.
CommandHandler	Common interface for all Command message handlers A command handler can choose support to 1 or more command types
EventBus	Simple event bus concept that supports both synchronous and asynchronous subscribers that are registered and listening for events published Usage example:
EventHandler	Common interface for all Event message handlers
Handler	Generic Method annotation that can be applied to any single argument method inside a AnnotatedCommandHandler or AnnotatedEventHandler. Depending on which class you extend the rules that apply to each method may be different. Common for all is that the method accessibility can be any combination of private, protected, public, etc.
LocalCommandBus	Provides a JVM local and non-durable, in regard to LocalCommandBus.sendAndDontWait(Object)/LocalCommandBus.sendAndDontWait(Object, Duration)), variant of the CommandBus concept
LocalEventBus	Simple event bus that supports both synchronous and asynchronous subscribers that are registered and listening for events published within the local the JVM You can have multiple instances of the LocalEventBus deployed with the local JVM, but usually one event bus is sufficient. Example:
LocalEventBus.Builder	Builder class for LocalEventBus.
LocalEventBus.EventPublishOverflowException
MultipleCommandHandlersFoundException
NoCommandHandlerFoundException
OnErrorHandler	Error Handler interface for the LocalEventBus's asynchronous event handler failures
ReactiveHandlersBeanPostProcessor	When using Spring or Spring Boot it will be easier to register the EventBus, CommandBus, CommandHandler and EventHandler instances as @Bean or @Component and automatically have the CommandHandler beans registered as with the single CommandBus bean and the EventHandler beans registered as subscribers with one or more EventBus beans.
SendAndDontWaitErrorHandler	Exception handler that will handle errors that occur during CommandBus.sendAndDontWait(Object)/CommandBus.sendAndDontWait(Object, Duration)
SendAndDontWaitErrorHandler.FallbackSendAndDontWaitErrorHandler	Fallback SendAndDontWaitErrorHandler that only error logs any issues. Note: If the SendAndDontWaitErrorHandler.FallbackSendAndDontWaitErrorHandler is used with a Durable Command Bus (e.g. using DurableQueues), then any failing command will not be retried. Instead use SendAndDontWaitErrorHandler.RethrowingSendAndDontWaitErrorHandler
SendAndDontWaitErrorHandler.RethrowingSendAndDontWaitErrorHandler	Fallback SendAndDontWaitErrorHandler that error logs any issues and rethrows the exception. The SendAndDontWaitErrorHandler.RethrowingSendAndDontWaitErrorHandler is compatible with a Durable Command Bus (e.g. using DurableQueues), as rethrowing the exceptions allows the command to be retried
SendCommandException