Untargeted Bindings

Creating bindings that don't have targets

You may create bindings without specifying a target. This is most useful for concrete classes and types annotated by either @ImplementedBy or @ProvidedBy. An untargeted binding informs the injector about a type, so it may prepare dependencies eagerly. Untargeted bindings have no to clause, like so:

    bind(MyConcreteClass.class);
    bind(AnotherConcreteClass.class).in(Singleton.class);

When specifying binding annotations, you must still add the target binding, even if it is the same concrete class. For example:

    bind(MyConcreteClass.class)
        .annotatedWith(Names.named("foo"))
        .to(MyConcreteClass.class);
    bind(AnotherConcreteClass.class)
        .annotatedWith(Names.named("foo"))
        .to(AnotherConcreteClass.class)
        .in(Singleton.class);

Untargeted bindings are often used to register a type in a Module to ensure that Guice is aware of the type. Registering those types is required to make them eligible for injection when JIT is disabled.

User's Guide
Common Guice Errors
Best Practices
Frequently Asked Questions
Integration
- Web and Servlets
- Google App Engine
- Persistence
- OSGi
- Struts 2 Integration
- Third Party Modules
Extensions
- Extending Guice
- Elements SPI
- Extensions SPI
- AssistedInject
- Custom Scopes
- Custom Injections
- Throwing Providers
- Graphing Guice Applications
- Testing Support
  - Bound Fields
Internals
Releases
- Guice 7.0.0
- Guice 6.0.0
- Guice 5.1.0
- Guice 5.0.1
- Guice 5.0.0
- Guice 4.2.3
- Guice 4.2.2
- Guice 4.2.1
- Guice 4.2
- Guice 4.1
- Guice 4.0
- Guice 3.0
- Guice 2.0
- Guice 1.0
Community