core-java
core-java copied to clipboard
SpineEventEngine
The Java implementation of the framework core
Either in addition to available `Iterator` API, or replacing it.
Currently, some of the Javadocs use `{@literal @}` to render the annotations in the code samples. It doesn't work in conjunction with `` and `{@code }`, as the resulting HTML...
... instead of being an instance reference in each entity.
Once the `Inbox` is introduced, the `ServerEnvironment` is going to get the server node identifier. However, in the upcoming code version, it is not going to be configurable. It should...
... 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, many messages in the framework have associated `Envelope` types, e.g. `CommandEnvelope`, `EventEnvelope`. This is semantic duplication. We should use interfaces with `(is)` option instead.
This is a notion of idea to include the custom security attributes into `SystemProperties`, a message initialized in the DMZ (such as HTTP Filter or gRPC server-side endpoint) and transferred...
The `SystemProperties` serves to supply messages such as `Command` with service information, required by the framework. In particular, the security-related attributes are planned to transfer within these properties. Currently `SystemProperties`...
Metadata
Owner
Metadata
The Java implementation of the framework core