Top Description Methods
com.google.inject

public Interface Module

Known Direct Implementers
com.google.inject.PrivateModule, com.google.inject.internal.ProviderMethodsModule, com.google.inject.internal.RealMapBinder, com.google.inject.internal.RealMapBinder.MultimapBinder, com.google.inject.internal.RealMultibinder, com.google.inject.internal.RealOptionalBinder, com.google.inject.internal.InjectorShell.RootModule, com.google.inject.internal.InjectorShell.InheritedScannersModule, com.google.inject.spi.Elements.ElementsAsModule, com.google.inject.util.Modules.EmptyModule, com.google.inject.util.Modules.CombinedModule, com.google.inject.util.Modules.RequireExplicitBindingsModule, com.google.inject.util.Modules.RequireAtInjectOnConstructorsModule, com.google.inject.util.Modules.RequireExactBindingAnnotationsModule, com.google.inject.util.Modules.DisableCircularProxiesModule, com.google.inject.AbstractModule
A module contributes configuration information, typically interface bindings, which will be used to create an Injector. A Guice-based application is ultimately composed of little more than a set of Modules and some bootstrapping code.

Your Module classes can use a more streamlined syntax by extending AbstractModule rather than implementing this interface directly.

In addition to the bindings configured via configure, bindings will be created for all methods annotated with @Provides. Use scope and binding annotations on these methods to configure the bindings.

Method Summary

Modifier and TypeMethod and Description
public void
configure(Binder binder)

Contributes bindings and other configurations for this module to binder.

Method Detail

configureback to summary
public void configure(Binder binder)

Contributes bindings and other configurations for this module to binder.

Do not invoke this method directly to install submodules. Instead use Binder#install(Module), which ensures that provider methods are discovered.