Steven van Beelen

Thanks for drafting up this issue with us, @maartenjanvangool. I think there's value in something like this, although I'd guess a final solution would have a slightly different API. What...

> Shouldn't integration tests cover this implicitly? Am I looking over something why this wouldn't be tested by integration tests? We just had a discussion about this in the team....

@benneq thanks for the suggestion and an understandable one at that. We however have taken the stance to choose our own solution instead of a ready made one *to not...

Maybe by providing some form of annotation, like `@EventAlias(String[] aliases)`? :thinking:

@benneq I am not yet sure how that would work and if it would work at all. This was just my thoughts roaming freely in regards to this issue. Further...

@benneq: We're currently hard at work resolving 4.1 along the entire Axon eco-system - this means a heavy focus on server. As soon as this is shored up, we will...

Thanks for sharing this with everybody here @JohT!

> After 2 and a half year, there is still no target release for this? Since creating this issue, the planning sessions have time and time again concluded that there...

Removed the milestone for now, as we will not be able to resolve this issue within release 4.6.0. We will adjust this ticket accordingly once we pick it up again.

Although a `RetryScheduler` for the `QueryGateway` is a great idea, the current position of the `RetryScheduler` is somewhat problematic. It's a part of the `org.axonframework.commandhandling`. Although this doesn't make it...