2e5193347e
* Getter for CurrentClusterState in Cluster extension, updated via ClusterReadView * Remove lazy init of readView. Otherwise the cluster.state will be empty on first access, wich is probably surprising * Subscribe to several cluster event types at once, to ensure *one* CurrentClusterEvent followed by change events * Deprecate publishCurrentClusterState, was a bad idea, use sendCurrentClusterState instead * Possibility to subscribe with InitialStateAsEvents to receive events corresponding to CurrentClusterState * CurrentClusterState not a ClusterDomainEvent, ticket #3614 |
||
|---|---|---|
| .. | ||
| akka-sample-camel-java | ||
| akka-sample-camel-scala | ||
| akka-sample-cluster-java | ||
| akka-sample-cluster-scala | ||
| akka-sample-fsm | ||
| akka-sample-hello-kernel | ||
| akka-sample-main-java | ||
| akka-sample-main-scala | ||
| akka-sample-multi-node | ||
| akka-sample-osgi-dining-hakkers | ||
| akka-sample-persistence/src/main | ||
| akka-sample-remote-java | ||
| akka-sample-remote-scala | ||