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 streamline
| 31 | * bindings. |
| 32 | */ |
| 33 | public interface Module { |
| 34 | |
| 35 | /** |
| 36 | * Contributes bindings and other configurations for this module to {@code binder}. |
| 37 | * <p> |
| 38 | * <strong>Do not invoke this method directly</strong> to install submodules. Instead use |
| 39 | * {@link Binder#install(Module)}, which ensures that {@link Provides provider methods} are |
| 40 | * discovered. |
| 41 | */ |
| 42 | void configure(Binder binder); |
| 43 | } |
no outgoing calls
no test coverage detected