Feature Description
Right now, users will need to register a SnapshotPolicy manually to trigger snapshotting for their event-sourced entities.
This is essentially our declarative configuration, that in AF4 was done through the AggregateConfigurer.
However, when users use Spring with the @EventSourced annotation, they'll not (want to) touch the declarative configuration.
For these use cases we should, instead, provide a solution through annotations to define that snapshots are desired.
An idea for this is to use the same approach as before, namely, that our Spring stereotype is able to refer to the bean name for wiring.
Current Behaviour
The SnapshotPolicy should be registered directly with an event-sourced entity.
Wanted Behaviour
There's a simple means to register SnapshotPolicy when using annotations.
Possible Workarounds
Feature Description
Right now, users will need to register a
SnapshotPolicymanually to trigger snapshotting for their event-sourced entities.This is essentially our declarative configuration, that in AF4 was done through the
AggregateConfigurer.However, when users use Spring with the
@EventSourcedannotation, they'll not (want to) touch the declarative configuration.For these use cases we should, instead, provide a solution through annotations to define that snapshots are desired.
An idea for this is to use the same approach as before, namely, that our Spring stereotype is able to refer to the bean name for wiring.
Current Behaviour
The
SnapshotPolicyshould be registered directly with an event-sourced entity.Wanted Behaviour
There's a simple means to register
SnapshotPolicywhen using annotations.Possible Workarounds