Nrthugu

I implemented a custom mechanism for integrating Akka with Spring as DI framework where I registered ActorSystem as a singleton-scoped bean:

@Configuration

internal open class SpringAkkaConfiguration

{

    @Bean

    open fun actorSystem(@Value("${akka.tcp.port}") akkaTcpPort: Int): ActorSystem

    {

        val config = ConfigFactory

            .defaultApplication()

            .withValue("akka.remote.netty.tcp.port", ConfigValueFactory.fromAnyRef(akkaTcpPort))

            .withValue("akka.remote.netty.tcp.hostname", ConfigValueFactory.fromAnyRef("localhost"))

            .withValue("akka.loglevel", ConfigValueFactory.fromAnyRef("WARNING"))



        return ActorSystem.create("system", config)

    }

}





@Component

internal class SpringActorSystem(private val actorSystem: ActorSystem,

                                 private val beanFactory: BeanFactory) : SpringAkka

{

    override fun announce(actorClass: Class<out Actor>): ActorRef

    {

        val props = Props.create(SpringIndirectActorProducer::class.java, beanFactory, actorClass)

        return actorSystem.actorOf(props, actorClass.simpleName)

    }

}

and within which I created two "Manager" actors using custom annotation @Actor, which indicates it's scope to "prototype":

@Target(AnnotationTarget.CLASS, AnnotationTarget.TYPE)

@Retention(AnnotationRetention.RUNTIME)

@Component

@Scope("prototype")

annotation class Actor





@Actor

internal class FirstManager(private val connectionService: ConnectionService) : AbstractActor()

{

    override fun createReceive(): Receive = receiveBuilder().build()

}





@Actor

internal class SecondManager(private val connectionService: ConnectionService) : AbstractActor()

{

    override fun createReceive(): Receive = receiveBuilder().build()

}

Each actor is picked up from IoC and registered in ActorSystem as a child, everything worked perfectly fine to the moment I came up with the idea of creating child actors to managers so hierarchy would look as follows:

-system

 - FirstManager

    -firstchild

    -secondchild

 -SecondManager

    -first-child

    -second-child

What would be a good solution for registering the following children to each manager but not to ActorSystem itself to build up mentioned hierarchy? Each child actor is dependant upon some other services and I would like to have a possibility to inject them without hassle. Example:

@Actor

internal class ChildActor(private val anotherService: AnotherService): AbstractActor()

{

    override fun createReceive(): Receive = receiveBuilder().build()

}