In more complex projects with multiple
Jdbi definitions, there are often elements (e.g. mappers or plugins) that should be shared between all
Modules that extend
AbstractJdbiConfigurationModule bind Jdbi related elements such as mappers, plugins, codecs etc. which then are used by Jdbi
definition modules (which extend
AbstractJdbiDefinitionModule). Any binding that is defined here will be added to any Jdbi definition as long as they
either use the same configuration annotation. By default (unless using the constructors that explicitly take an annotation), all Jdbi definitions have all
This module does neither define a Jdbi binding nor requires a data source to be bound. Jdbi instances are defined in modules extending
AbstractJdbiDefinitionModule (which are private guice modules).
AbstractJdbiConfigurationModulepublic AbstractJdbiConfigurationModule()Creates an element configuration module.
All elements defined in this module will be bound using the
JdbiGlobalannotation. This is the used by
AbstractJdbiDefinitionModuleinstances unless a custom annotation is used.
AbstractJdbiConfigurationModuleCreates an element configuration module with a custom annotation.
All elements defined in this module will be bound using the given custom annotation. This allows creating multiple sets of element configuration modules which can be referenced from modules extending the
AbstractJdbiDefinitionModulebase class if a the same custom annotation is used.