Steven van Beelen

Of course we'll keep it open @OLibutzki! Let us know as soon as you've had to chance to look into this.

By the way, I've checked whether the Reference Guide stated the setting of the repository when using Spring. You can find the bit I've just described [here](https://docs.axoniq.io/reference-guide/configuring-infrastructure-components/command-processing/command-model-configuration#command-model-repositories).

Reopening seems reasonable to me, so let's do that :-)

First, thanks for showing interest in the feature @jurgenbosch! To come to your question, we typically update issues accordingly when work is progressing or has happened on them. As it...

Great plan, which sounds like an easy enough feature to introduce by anybody. Hence why I added "ideal for contribution". Whilst _anybody_ would be at it, I'd suggest to add...

As far as "official" goes, I'd take the [SQLErrorCode](https://github.com/AxonFramework/AxonFramework/blob/master/eventsourcing/src/main/resources/org/axonframework/eventsourcing/eventstore/jpa/SQLErrorCode.properties) as a guideline.

@abuijze / @m1l4n54v1c do we still want to introduce a `PageResponseType` as an implementation of the `ResponseType` interface to be used in the `QueryBus`?

Definitely a fair share @jokefaker, thanks for that! As it stands however, the `ResponseType` implementations Axon provide will likely ignore any generics added in an already existing `Page` implementation. Thus,...

We follow a similar pattern with wrappers classes as you're suggesting @Blackdread on the subscription query. We utilize project-reactor for that, but do not want to force users to pull...

You are always more then welcome to contribute @Blackdread! Once you feel you are ready for it, we'll see the PR coming our way. And if not, then we will...