Binding `Play.current.configuration` using dependency injection in Play 2.5?

98 views Asked by At

I'm using Guice dependency injection in my Play 2.5 application, along with SecureSocial. SecureSocial's Registration controller calls a (deprecated) Play.current.configuration value eagerly, which so far as I can tell is incompatible with DI, and therefore I get a java.lang.RuntimeException: There is no started application error immediately at runtime. Is there a way I can ensure that Play.current.configuration is bound by Guice and thus available to the SecureSocial library? Or is my only option to re-write the Registration controller to call the configuration lazily?

1

There are 1 answers

1
Andriy Kuba On

SecureSocial is on the way to support Play 2.5

There is a 3.0-M6 version (12 days ago), did you try it?

https://groups.google.com/forum/#!topic/securesocial/YcrAay9eO2M

https://github.com/jaliss/securesocial