Steven van Beelen

Good, sensible points @anno1985, we'll look into aligning one another some time soon. So, thanks for filing this issue with us!

Your voice is heard @janesser, and I feel you've got a good suggestion here. We've been discussing such a topic internally too; as soon as it's also the users who're...

Thanks for marking this idea @janesser. We'll take a stab at figuring out how to best fit this in the guide. FYI: Changes are that this original ticket you've created...

I have validated @CodeDrivenMitch his statement to be correct, although it is important to note that one event is contained in the `givenEvents` collection and the other in the `publishedEvents`...

Closing this issue, since it's been resolved by #3056.

I agree with the suggestion to look into the subject for Axon Framework 5, since, as concluded already, Axon Framework 4 does not enforce the `@EntityId` annotation for non-collection aggregate...

I have renamed the issue to "Use EntityId on non-collection Aggregate Members for routing" as this will make it clearer on our internal board what the intended work is with...

This issue is being tackled as part of #3068 to revise the aggregate modelling support. More specifically, the renewed `CommandTargetResolver`, introduced in #3457, makes it so that non-collections entities also...

As far as I understand the situation, the way to resolve this would be by introducing a `AxonServerConnectionDetails` implementation purely for the property-based injection, correct? So, something like `PropertiesAxonServerConnectionDetails`, to...

Thanks for that, @oleborne. I was able to reproduce the failing test in Axon Framework, so that's a plus. Digging through the Spring Boot code, it seems as if the...