Guice

I'm starting a new Java web app from scratch. I don't have much experience on Spring Framework, but I know I'd like to use some of its features, such as Transaccions Management. On the other hand, I really like Guice for dependency injection. I know that Guice and Spring can work together: http://www.jroller.com/mindcrime/entry/an_example_of_integrating_guice But before starting designing my application, I wanted to know if someone had experienced issues by following that approach. Also, what I really like from Guice is that you don't need an XML configuration file, but just java Modules,

I have a generic database access class, which i'm binding using the TypeLiteral construct. Now in a test i want to mock that class and i have therefor created a Provider, that creates a mock instance. In my test, i want to access that mock to define its behaviour. Now the question is, how can i retrieve the object from the injector? That's my binding definition: binder.bind(new TypeLiteral<GenericDbClass<Integer>>(){}).GenericDbClassProvider.class); Normally i would get an instance like this: injector.getInstance(GenericDbClass.class); But since i'm not binding the implementation of

What does the method install() from the AbstractModule class do? Can someone explain it to me? From the docs I read from the guice site all I could get was: Uses the given module to configure more bindings. Configure what bindings exactly? The bindings from the installed module or the bindings of the class that invoked the install method? install allows for composition: Within its configure method, FooModule may install FooServiceModule (for instance). This would mean that an Injector created based only on FooModule will include bindings and providers in both FooModule and FooServiceModule.

I know that this problem has been around for at least 3 yeears ( Issue 92 ), but I'm still not satisfied with the current state of it. I am also aware that this does not affect Tomcat if you do restart after redeploying (as suggested in Guice + Tomcat potential memory leak ). My problem is that I am experiencing OutOfMemoryError: PermGen errors after some redeployments. Notice that I am not using google-collections explicitly, I am only using Guice 3.0 (via maven). After analyzing heap dumps, I still see that the thread com.google.inject.internal.Finalizer is still active, keeps a reference to

In guice, the @Singleton scope does not refer to the Singleton pattern. According to the "Dependency Injection" book of "Dhanji" : Very simply, a singleton’s context is the injector itself. The life of a singleton is tied to the life of the injector (as in figure 5.8). Therefore, only one instance of a singleton is ever created per injector. It is important to emphasize this last point, since it is possible for multiple injectors to exist in the same application. In such a scenario, each injector will hold a different instance of the singleton-scoped object. Is it possible to share the same

I am trying to migrate a small project, replacing some factories with Guice (it is my first Guice trial). However, I am stuck when trying to inject generics. I managed to extract a small toy example with two classes and a module: import com.google.inject.Inject; public class Console<T> { private final StringOutput<T> out; @Inject public Console(StringOutput<T> out) { this.out = out; } public void print(T t) { System.out.println(out.converter(t)); } } public class StringOutput<T> { public String converter(T t) { return t.toString(); } } import com.google.inject.AbstractModule; import com.google

If I have interface Validator and multiple implementations for this interface. How can I inject any of the multiple implementations with Guice? Now I know that I can use following code to inject one, but it allows only one implementation: public class MyModule extends AbstractModule { @Override protected void configure() { bind(Validator.class).to(OneOfMyValidators.class); } } What I would like to do is: Validator v1 = injector.getInstance(Validator1.class); Validator v2 = injector.getInstance(Validator2.class); Is it possible at all? Andrew McNamee Short answer: binding annotations. They're