Thanks. It would really works that way. On the other hand its a kind of awkward workaround. I already have the configured connection context object at hand. I get it via dependency injection and would like to pass it to the extension or actor system directly.
Since I cannot pass objects of arbitrary type to a typesafe config object with this approach I need to acquire the configuration of the connection context. Than pass it to a typesafe config object. Which is passed to the actor system. Than I acquire it in the extension in order to recreate the db connection context again. Sounds quite complicated and prone to error. Potentially the connection context object is duplicated and I would end with two connections to one db. Which is not critical but quite undesirable. Leslie -- >>>>>>>>>> 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 https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
