core-java icon indicating copy to clipboard operation
core-java copied to clipboard

The Java implementation of the framework core

Results 96 core-java issues
Sort by recently updated
recently updated
newest added

This PR addresses #1313. The issue appears when multiple messages are dispatched from `Inbox`. Under the hood, those messages are processed as a batch, which triggers `Aggregate` to be cached...

This PR brings better documentation for the implemented gRPC services.

They fail at GitHub far too often.

tech debt
/Build

Suppose, we have an aggregate with ID of type `EntityOneId`. It produces events that have the first field of this type (and, of course, `producerId` in the `EventContext`). Some of...

enhancement
/Routing

Are they used by our current customers? They seem hard to explain and support. Enrichments are also not guaranteed at the receiving side. Therefore the code which deal with them...

/Enrichment

In a multi-tenant environment most likely some of the non Spine services will be multi-tenant as well. Currently, there is no way to easily implement a custom tenant-aware service. As...

enhancement

Spine `1.7.1` If you mistakenly create a command via `ActorRequestFactory` with `tenantId` that targets single-tenant BC. And post this command directly to `CommandService` via `post(Command request, StreamObserver responseObserver)`. Response observer...

bug

[This InfoQ article](https://www.infoq.com/news/2022/08/cloud-functions-2nd-gen-ga/) mentions the [CloudEvents standard](https://cloudevents.io/) as a nice feature of 2nd version of GCP Cloud Functions. We may review the [CloudEvents specs](https://github.com/cloudevents/spec/blob/main/cloudevents/spec.md) to see if our Protobuf types...

## Intro From a simplified point of view, dispatching of a command to an `Aggregate` consists of two main steps: 1. Sending a command to a dedicated [command-handling](https://github.com/SpineEventEngine/core-java/blob/master/server/src/main/java/io/spine/server/command/Assign.java) method. 1.1....

During implementation of #1436 some unused declarations were revealed. To address this issue, one should review the "unused" pieces. And either remove them, or suppress the warning with a corresponding...