raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 10

bump version to 2.5-SNAPSHOT (#21946)

Browse source 
* project/scripts/find-replace 2.4-SNAPSHOT 2.5-SNAPSHOT
This commit is contained in:
Patrik Nordwall 2016-12-05 10:43:29 +01:00 • committed by Konrad Malawski
parent 9647dd61fa
commit 9cd5046e1f
54 changed files with 128 additions and 128 deletions
Download patch file Download diff file Expand all files Collapse all files

6
akka-samples/akka-sample-persistence-java/tutorial/index.html
View file

@ -9,7 +9,7 @@
<h2>Akka Persistence Samples</h2>
<p>
This tutorial contains examples that illustrate a subset of
<a href="http://doc.akka.io/docs/akka/2.4-SNAPSHOT/java/persistence.html" target="_blank">Akka Persistence</a> features.
<a href="http://doc.akka.io/docs/akka/2.5-SNAPSHOT/java/persistence.html" target="_blank">Akka Persistence</a> features.
</p>
<ul>
<li>persistent actor</li>
@ -28,7 +28,7 @@ Custom storage locations for the journal and snapshots can be defined in
<h2>Persistent actor</h2>
<p>
<a href="#code/src/main/java/sample/persistence/PersistentActorExample.java" class="shortcut">PersistentActorExample.java</a>
is described in detail in the <a href="http://doc.akka.io/docs/akka/2.4-SNAPSHOT/java/persistence.html#event-sourcing-java" target="_blank">Event sourcing</a>
is described in detail in the <a href="http://doc.akka.io/docs/akka/2.5-SNAPSHOT/java/persistence.html#event-sourcing-java" target="_blank">Event sourcing</a>
section of the user documentation. With every application run, the <code>ExamplePersistentActor</code> is recovered from
events stored in previous application runs, processes new commands, stores new events and snapshots and prints the
current persistent actor state to <code>stdout</code>.
@ -78,7 +78,7 @@ in the case where you persist a command that corrupts your state. The corrupt co
to delete the corrupt commands from the journal.
</p>
<p>
In an <a href="http://doc.akka.io/docs/akka/2.4-SNAPSHOT/java/persistence.html#event-sourcing" target="_blank">event sourced</a>
In an <a href="http://doc.akka.io/docs/akka/2.5-SNAPSHOT/java/persistence.html#event-sourcing" target="_blank">event sourced</a>
system, one does not persist commands directly but rather events that have been derived from received commands
(not shown here). These events are known to be successfully applicable to current processor state i.e. there's
no need for deleting them from the journal. Event sourced processors usually have a lower throughput than command