From 7bd9550e3b9a872cf6d1116eda45663ec6e6c1f4 Mon Sep 17 00:00:00 2001 From: Patrik Nordwall Date: Wed, 1 Jul 2015 14:49:06 +0200 Subject: [PATCH] =clu #16897 Correct wording for routees.paths --- .../main/scala/akka/cluster/routing/ClusterRouterConfig.scala | 2 +- akka-docs/rst/java/cluster-usage.rst | 3 ++- akka-docs/rst/scala/cluster-usage.rst | 3 ++- 3 files changed, 5 insertions(+), 3 deletions(-) diff --git a/akka-cluster/src/main/scala/akka/cluster/routing/ClusterRouterConfig.scala b/akka-cluster/src/main/scala/akka/cluster/routing/ClusterRouterConfig.scala index 437abaef06..0b0e55da53 100644 --- a/akka-cluster/src/main/scala/akka/cluster/routing/ClusterRouterConfig.scala +++ b/akka-cluster/src/main/scala/akka/cluster/routing/ClusterRouterConfig.scala @@ -61,7 +61,7 @@ final case class ClusterRouterGroupSettings( routeesPaths.foreach(p ⇒ p match { case RelativeActorPath(elements) ⇒ // good case _ ⇒ - throw new IllegalArgumentException(s"routeesPaths [$p] is not a valid relative actor path") + throw new IllegalArgumentException(s"routeesPaths [$p] is not a valid actor path without address information") }) } diff --git a/akka-docs/rst/java/cluster-usage.rst b/akka-docs/rst/java/cluster-usage.rst index 4dc82f376f..f5f84e0d0b 100644 --- a/akka-docs/rst/java/cluster-usage.rst +++ b/akka-docs/rst/java/cluster-usage.rst @@ -454,7 +454,8 @@ That is not done by the router. The configuration for a group looks like this: The routee actors should be started as early as possible when starting the actor system, because the router will try to use them as soon as the member status is changed to 'Up'. -The relative actor paths defined in ``routees.paths`` are used as for selecting the actors to which the messages will be forwarded to by the router. +The actor paths without address information that are defined in ``routees.paths`` are used for selecting the +actors to which the messages will be forwarded to by the router. Messages will be forwarded to the routees using :ref:`ActorSelection `, so the same delivery semantics should be expected. It is possible to limit the lookup of routees to member nodes tagged with a certain role by specifying ``use-role``. diff --git a/akka-docs/rst/scala/cluster-usage.rst b/akka-docs/rst/scala/cluster-usage.rst index 234184767e..19c923f25c 100644 --- a/akka-docs/rst/scala/cluster-usage.rst +++ b/akka-docs/rst/scala/cluster-usage.rst @@ -451,7 +451,8 @@ That is not done by the router. The configuration for a group looks like this: The routee actors should be started as early as possible when starting the actor system, because the router will try to use them as soon as the member status is changed to 'Up'. -The relative actor paths defined in ``routees.paths`` are used as for selecting the actors to which the messages will be forwarded to by the router. +The actor paths without address information that are defined in ``routees.paths`` are used for selecting the +actors to which the messages will be forwarded to by the router. Messages will be forwarded to the routees using :ref:`ActorSelection `, so the same delivery semantics should be expected. It is possible to limit the lookup of routees to member nodes tagged with a certain role by specifying ``use-role``.