#2709 - Adding documentation for wildcards in deployments.

This commit is contained in:
Viktor Klang 2012-11-28 10:56:08 +01:00
parent e8610e1ddd
commit 3a3dad5c53
2 changed files with 18 additions and 0 deletions

View file

@ -122,6 +122,15 @@ actor systems has to have a JAR containing the class.
object, which in most cases is not serializable. It is best to make a static
inner class which implements :class:`UntypedActorFactory`.
.. note::
You can use asterisks as wildcard matches for the actor path sections, so you could specify:
``/*/sampleActor`` and that would match all ``sampleActor`` on that level in the hierarchy.
You can also use wildcard in the last position to match all actors at a certain level:
``/someParent/*``. Non-wildcard matches always have higher priority to match than wildcards, so:
``/foo/bar`` is considered **more specific** than ``/foo/*`` and only the highest priority match is used.
Please note that it **cannot** be used to partially match section, like this: ``/foo*/bar``, ``/f*o/bar`` etc.
.. warning::
*Caveat:* Remote deployment ties both systems together in a tight fashion,

View file

@ -129,6 +129,15 @@ actor systems has to have a JAR containing the class.
most cases is not serializable. It is best to create a factory method in the
companion object of the actors class.
.. note::
You can use asterisks as wildcard matches for the actor paths, so you could specify:
``/*/sampleActor`` and that would match all ``sampleActor`` on that level in the hierarchy.
You can also use wildcard in the last position to match all actors at a certain level:
``/someParent/*``. Non-wildcard matches always have higher priority to match than wildcards, so:
``/foo/bar`` is considered **more specific** than ``/foo/*`` and only the highest priority match is used.
Please note that it **cannot** be used to partially match section, like this: ``/foo*/bar``, ``/f*o/bar`` etc.
.. warning::
*Caveat:* Remote deployment ties both systems together in a tight fashion,