Merge pull request #30137 from johanandren/wip-crosslink-coexistance-top-level-spawn

Crosslink and extra sentence about top level spawn in from-classic
This commit is contained in:
Patrik Nordwall 2021-03-29 10:55:30 +02:00 committed by GitHub
commit aaeb6ec591
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 0 deletions

View file

@ -103,6 +103,8 @@ Scala
Java
: @@snip [TypedWatchingClassicTest.java](/akka-actor-typed-tests/src/test/java/jdocs/akka/typed/coexistence/TypedWatchingClassicTest.java) { #classic }
<a id="top-level-typed-actor-classic-system"></a>
Creating the actor system and the typed actor:
Scala

View file

@ -117,6 +117,9 @@ for creating top level actors. Instead, there is a single top level actor define
when starting the `ActorSystem`. Other actors are started as children of that user guardian actor or
children of other actors in the actor hierarchy. This is explained more in @ref:[ActorSystem](#actorsystem).
Note that when mixing classic and typed and have a classic system, spawning top level actors from the side is possible, see
@ref:[Coexistence](coexisting.md#top-level-typed-actor-classic-system).
The `actorOf` method takes an `akka.actor.Props` parameter, which is like a factory for creating the actor instance, and it's
also used when creating a new instance when the actor is restarted. The `Props` may also define additional
properties such as which dispatcher to use for the actor.