Docs: don't use $code$ for now in doc snippets
This commit is contained in:
parent
83c7894514
commit
a84a18d262
1 changed files with 4 additions and 4 deletions
|
|
@ -429,19 +429,19 @@ This is expected behavior. When the node has been accepted in the cluster you wi
|
||||||
receive `MemberUp` for that node, and other nodes.
|
receive `MemberUp` for that node, and other nodes.
|
||||||
|
|
||||||
Scala
|
Scala
|
||||||
: @@snip [SimpleClusterListener2.scala]($code$/scala/docs/cluster/SimpleClusterListener2.scala) { #join #subscribe }
|
: @@snip [SimpleClusterListener2.scala](/akka-docs/src/test/scala/docs/cluster/SimpleClusterListener2.scala) { #join #subscribe }
|
||||||
|
|
||||||
Java
|
Java
|
||||||
: @@snip [SimpleClusterListener2.java]($code$/java/jdocs/cluster/SimpleClusterListener2.java) { #join #subscribe }
|
: @@snip [SimpleClusterListener2.java](/akka-docs/src/test/java/jdocs/cluster/SimpleClusterListener2.java) { #join #subscribe }
|
||||||
|
|
||||||
To avoid receiving an empty `CurrentClusterState` at the beginning, you can use it like shown in the following example,
|
To avoid receiving an empty `CurrentClusterState` at the beginning, you can use it like shown in the following example,
|
||||||
to defer subscription until the `MemberUp` event for the own node is received:
|
to defer subscription until the `MemberUp` event for the own node is received:
|
||||||
|
|
||||||
Scala
|
Scala
|
||||||
: @@snip [SimpleClusterListener2.scala]($code$/scala/docs/cluster/SimpleClusterListener2.scala) { #join #register-on-memberup }
|
: @@snip [SimpleClusterListener2.scala](/akka-docs/src/test/scala/docs/cluster/SimpleClusterListener2.scala) { #join #register-on-memberup }
|
||||||
|
|
||||||
Java
|
Java
|
||||||
: @@snip [SimpleClusterListener2.java]($code$/java/jdocs/cluster/SimpleClusterListener2.java) { #join #register-on-memberup }
|
: @@snip [SimpleClusterListener2.java](/akka-docs/src/test/java/jdocs/cluster/SimpleClusterListener2.java) { #join #register-on-memberup }
|
||||||
|
|
||||||
|
|
||||||
If you find it inconvenient to handle the `CurrentClusterState` you can use
|
If you find it inconvenient to handle the `CurrentClusterState` you can use
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue