Package ru.vyarus.dropwizard.guice.module.installer

Class CoreInstallersBundle

java.lang.Object

ru.vyarus.dropwizard.guice.module.context.unique.item.UniqueGuiceyBundle

ru.vyarus.dropwizard.guice.module.installer.CoreInstallersBundle

All Implemented Interfaces:

GuiceyBundle

public class CoreInstallersBundle
extends UniqueGuiceyBundle

Core installers bundle. Installs WebInstallersBundle.

Since:

02.08.2015

Constructor Summary

Constructors

Constructor	Description
CoreInstallersBundle()

Method Summary

Modifier and Type	Method	Description
void	initialize(GuiceyBootstrap bootstrap)	Called in initialization phase.

Methods inherited from class ru.vyarus.dropwizard.guice.module.context.unique.item.UniqueGuiceyBundle

equals, hashCode

Methods inherited from class java.lang.Object

clone, finalize, getClass, notify, notifyAll, toString, wait, wait, wait

Methods inherited from interface ru.vyarus.dropwizard.guice.module.installer.bundle.GuiceyBundle

run

Constructor Detail

CoreInstallersBundle

public CoreInstallersBundle()

Method Detail

initialize

public void initialize(GuiceyBootstrap bootstrap)

Description copied from interface: GuiceyBundle

Called in initialization phase. GuiceyBootstrap contains almost the same methods as GuiceBundle.Builder, which allows registering installers, extensions and guice modules. Existing installer could be replaced by disabling old one and registering new.

Dropwizard bundles could be also registered with GuiceyBootstrap.dropwizardBundles(io.dropwizard.core.ConfiguredBundle[]) shortcut (or by directly accessing dropwizard bootstrap object: GuiceyBootstrap.bootstrap().

As bundles could be registered only during initialization phase, it is not possible to avoid bundle registration based on configuration (not a good practice). But, it is possible to use guicey options instead: for example, map option from environment variable and use to decide if some bundles should be activated.

Parameters:

bootstrap - guicey bootstrap object