Alexander Yevsyukov
Alexander Yevsyukov
Currently, `EventContext` only contains information about the time-zone of the `Origin` of the event. Presumably most frequent example of this is the time-zone of the user who created the command...
Either in addition to available `Iterator` API, or replacing it.
... instead of being an instance reference in each entity.
... take it from a `BoundedContext` into which the bus is inserted. A bus cannot have a different setting. So there's no sense in the API for configuring it in...
Now we user the `ActorContext` of incoming message for obtaining a user ID on behalf of whom a command would be generated. We need to support a way for setting...
Currently, we can only delay a command by certain `Duration`. `CommandContext.Schedule` should be extended with the following fields: * `at` which would specify date/time. Presumably, it would be `LocalDateTime` value...
Methods like `receivesCommand()`, `receivesCommands()`, `importsEven()`, `importsEvents()` should receive specific message types. There can be methods that accept `Command` or `Event`, but since they cannot be casted to `CommandMessage` or `EventMessage`,...
The import arrangement provided by `ImportBus` allows to import events as they occur. # Limitations of the dispatch-based approach The dispatch-based import does not allow to safely import events that...
It may help clarify the meaning the API and help in case of using together with a dependency injection framework.