=per native typed implementation of Eventsourced=>PersistendBehavior
timeout is explicitly a message of Command persitAll and chainable side effects work well more tests pasing additional sanity check that mutable behaviors work as expected unstashing needs to "loop through" the AdapterActor otherwise Stopped won't work solve unstashing/stop issue, by not randomly init()ing, but unstashing snapshotting works all tests green rebased nicer log source remove IncomingCommand wrapper, we dont need it no need for shared counter remove not needed methods and state more state cleanup, using Behaviors.same reminder that we DO need that same alias, since stash does not work with the Behavior.same introduce config for stash buffer stopping now works after persisting compile fix cleanup reduced number of adapter styles needed for co-existence of persistence final cleanup done, less passing around 40 objects, carriers provided now
This commit is contained in:
parent
907c6a6931
commit
70e225b734
43 changed files with 1696 additions and 532 deletions
|
|
@ -62,8 +62,10 @@ and can be used to create various effects such as:
|
|||
|
||||
External side effects can be performed after successful persist with the `andThen` function e.g
|
||||
@scala[`Effect.persist(..).andThen`]@java[`Effect().persist(..).andThen`].
|
||||
In the example below a reply is sent to the `replyTo` ActorRef. Note that the new state after applying
|
||||
the event is passed as parameter to the `andThen` function.
|
||||
|
||||
In the example below a reply is sent to the `replyTo` ActorRef. Note that the new state after applying
|
||||
the event is passed as parameter to the `andThen` function. All `andThen*` registered callbacks
|
||||
are executed after successful execution of the persist statement (or immediately, in case of `none` and `unhandled`).
|
||||
|
||||
### Event handler
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue