Guice

I read Dependency Injection Without the Gymnastics PDF which indicates there's no need for any fancy DI framework, but it's beyond my grasp (at least without concrete examples). I'll try watching Dependency Injection Without the Gymnastics and Dead Simple Dependency Injection when I have a chance. Using Guice in Java, if A depends on both B and C and both B and C depend on D, one would have something like: public class A { @Inject public A(B b, C c) { this.b = b; this.c = c; } } public class B { @Inject public B(D d) { this.d = d; } } public class C { @Inject public C(D d) { this.d = d; } }

I am currently building a Dropwizard + Guice + Jersey-based application where the database access is being handled by JDBI for the time being. What I am trying to achieve is to have your typical enterprise architecture, where Resources access Service classes accessing a DAO class that in turn accesses the database. It would be nice to get all this wired up in a proper DI way, although I guess I can build my object graph in the run() method of the application if all else fails. So, I'm running into this problem that has been mentioned here before : Getting a DBIFactory requires both the

I'm having some troubles understanding how Guice's singleton instantiations works. I've read the available documentation (here - http://code.google.com/p/google-guice/wiki/Scopes ), but I still can't figure out some things: 1) I've integrated Guice with Tomcat, and I've set up some bindings in a ServletModule: bind(MyServlet.class).asEagerSingleton(); serve("myUrl").with(MyServlet.class); serve("myOtherUrl").with(MyOtherServlet.class); (where MyOtherServlet class has a @Singleton annotation above it) My intention here was to have two servlets, where one is eagerly instantiated, while the other

Java 8, Guice 4.0 and Akka 2.3.9 here. I am trying to figure out how to annotate my actor classes with JSR330-style @Inject annotations, and then wire them all up via Guice. But literally every single article I have read (some examples below) either uses Scala code examples, a criminally-old version of Guice, or a criminally-old version of Akka: Let It Crash Scala-Guice So, given the following Guice module: public interface MyService { void doSomething(); } public class MyServiceImpl implements MyService { @Override public void doSomething() { System.out.println("Something has been done!"); }

I'm not sure if there is merit to this question or not, but are there any best practices and anti-patterns specific to Google Guice ? Please direct any generic DI patterns to this question . I have always felt that constructor injection to final fields is a best practice. It minimizes mutable state and makes the class easier to understand by making the class's formal dependencies explicit. public class MyClass { private final MyDependency dependency; @Inject public MyClass(MyDependency dependency) { this.dependency = dependency; } } Kevin Bourrillion There are some on the Guice project page.