Steven van Beelen

Results 165 issues of Steven van Beelen

It would be beneficial to introduce a dedicated `Command Execution Exception` page under [Implementing Domain Logic/Command Handling](https://docs.axoniq.io/reference-guide/implementing-domain-logic/command-handling). This would describe some approach to throwing exceptions from Command Handlers, what would...

Priority 3: Could
Type: Feature

There currently is no section describing in depth all the configurable options for Axon Server on the side of Axon Framework. This should be included, likely in the AF portions...

Priority 1: Must
Type: Feature

The `MessageHandlingMember` currently has it's annotation specific methods deprecated. This is done because the interface should not be reflection specific at all, but allow for different approaches of receiving handler...

Type: Enhancement
Priority 2: Should

This pull request does numerous things for the `MessageStream` interface and its implementations. A large part is "cleanup and finetuning," which includes variable/parameter/method/class renaming, JavaDoc additions and expansion, indentation changes,...

Type: Enhancement
Priority 1: Must

### Enhancement Description Give the intent that the `MessageStream` API will completely replace the use of the response messages, with additional functionality attached to it where applicable, it becomes a...

Type: Enhancement
Priority 1: Must

When using an event-sourced aggregate, the framework uses the so-called `AggregateFactory` to construct an Aggregate instance. However, it is _only_ used when there are events present for the aggregate. Thus,...

Type: Enhancement
Priority 2: Should

### Description Instead of using the fully qualified class names as payload types for the messages, we could (for example) use a combination of context, aggregate type (if applicable), and...

Type: Feature
Priority 1: Must

### Enhancement Description We should adjust the `EventStore` and `EventStorageEngine` to be in line with the new Unit of Work, `ProcessingContext`, and `MessageStream` API (as introduced in #2953). This would...

Type: Enhancement
Priority 1: Must

### Enhancement Description As it stands, the introduction from #2965 and #3003 were great first steps towards a new approach to the Command Bus, but several components are still missing....

Type: Enhancement
Priority 2: Should

Having some form of explicit message schema support would be a nice addition to Axon Framework. Whether this would be Protobuf, Avro, JSON schema, Thrift, or other tools we can...

Type: Feature
Status: Under Discussion