Enhancement Description
We should align the Persistent Stream support with Axon Server to Axon Framework's renewed Async Native API.
Differently put, the current Persistent Stream implementation should:
- Work well with the new Unit of Work
- Become a subscribable
MessageStream
- Work through the new Configuration API
Although the new DCB-based event store allows filtering through the EventCriteria, know that at this stage the persistent stream API allows this filtering to happen at the client, not at the server!
Configuration of Persistent Streams should be ingrained into Axon's configuration and the Spring Boot configuration as part of this issue. Take not to ensure the flows as described for Axon Framework 4 have their equivalent in Axon Framework 5. Thus, included full autoconfiguration of Persistent Streams for each Event Processor, thus switching every Event Processor to a SubscribingEventProcessor. This latter part can easily be fulfilled as a separate PR done at the end.
Note
When picking up this issue, be sure to look for TODOs referring to this issue's issue number.
Current Behaviour
The Persistent Stream implementation uses old Axon Framework APIs.
Wanted Behaviour
The Persistent Stream implementation uses the new Axon Framework APIs.
Possible Workarounds
None
Enhancement Description
We should align the Persistent Stream support with Axon Server to Axon Framework's renewed Async Native API.
Differently put, the current Persistent Stream implementation should:
MessageStreamAlthough the new DCB-based event store allows filtering through the
EventCriteria, know that at this stage the persistent stream API allows this filtering to happen at the client, not at the server!Configuration of Persistent Streams should be ingrained into Axon's configuration and the Spring Boot configuration as part of this issue. Take not to ensure the flows as described for Axon Framework 4 have their equivalent in Axon Framework 5. Thus, included full autoconfiguration of Persistent Streams for each Event Processor, thus switching every Event Processor to a
SubscribingEventProcessor. This latter part can easily be fulfilled as a separate PR done at the end.Note
When picking up this issue, be sure to look for TODOs referring to this issue's issue number.
Current Behaviour
The Persistent Stream implementation uses old Axon Framework APIs.
Wanted Behaviour
The Persistent Stream implementation uses the new Axon Framework APIs.
Possible Workarounds
None