I'd like to know if there is some pattern to handle dynamic dependency injection.
This concern the situation where we have supervision hierarchy. Let say I have a service Z that depend on a service c which is part of the a -> b -> c hierarchy. Clearly Z does not own C, but would appreciate to use c. It seems to me that Z needs to know that hierarchy in advance. In a sense that would defeat the all purpose of dependency injection. I don't want to couple Z to know that hierarchy. It may change in the future. So I wonder how this kind of things work in general ? I am thinking of using some configuration file, where this kind of information would be set. In other words, the architecture of the system would not be hardwire in the actor, but provided in a configuration, that the actor could use to request the service he needs. -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
