Steven van Beelen

Moving this pull request to release 4.8.0, so we can implement a workable integration with Spring for decorators on Axon Framework's infrastructure components.

Time doesn't allow us to introduce this change into 4.8.0. Hence, I've removed the milestone.

Closing this issue due to inactivity.

Although I get where this is coming from, I don't think we should expand the `@ProcessingGroup` annotation for this. The Processing Group should not dictate the configuration of the Event...

I think the idea makes sense, @vab2048, but perhaps we need to look for another annotation or a different configuration approach. I'll leave it open for now. I am confident...

First off, thanks for filing this concern with us, @yitizi. Secondly, perhaps an obvious pointer, but [Axon Framework 4.4.5](https://github.com/AxonFramework/AxonFramework/releases/tag/axon-4.4.5) is an old version (November 2020) of Axon Framework, as we...

> Thanks for the reply. You suggested that I update the Axon Framework to the newest version, but the application is already published in production, so the update cannot be...

Closing this issue due to inactivity. But, be sure to reach out if it occurs again, @yitizi! In that case, we will reopen the issue to deal with it further.

We made the `ReplayAwareMessageHandlerWrapper` more closed in the past because, back then, it made sense. However, we would like to service the behavior you've implemented in an easier fashion where...

### Cause I think this happens because you have a massive aggregate, @unisteven. The fact it's big _very likely_ means it handles numerous commands, potentially at the same time. Due...