App
Related Doc:
package app
ONLY INTENDED FOR USE BY THE FRAMEWORK.
ONLY INTENDED FOR USE BY THE FRAMEWORK.
Default modules can be overridden in production by overriding methods in your App or Server.
We take special care to make sure the module is not null, since a common bug is overriding the default methods using a val instead of a def
ONLY INTENDED FOR USE BY THE FRAMEWORK.
ONLY INTENDED FOR USE BY THE FRAMEWORK.
ONLY INTENDED FOR USE BY THE FRAMEWORK.
ONLY INTENDED FOR USE BY THE FRAMEWORK.
Method to be be called after port warmup
Method to be be called after port warmup
Method to be called after successful warmup but before application initialization
Method to be called after successful warmup but before application initialization
Production modules from Java
Production modules from Java
ONLY INTENDED FOR USE IN TESTING.
ONLY INTENDED FOR USE IN TESTING.
Override modules from Java which redefine production bindings (only use overrideModules during testing) If you think you need this in your main server you are most likely doing something incorrectly.
ONLY INTENDED FOR USE BY THE FRAMEWORK.
ONLY INTENDED FOR USE BY THE FRAMEWORK.
DO NOT BLOCK
Production modules
Production modules
ONLY INTENDED FOR USE IN TESTING.
ONLY INTENDED FOR USE IN TESTING.
Override modules which redefine production bindings (only use overrideModules during testing) If you think you need this in your main server you are most likely doing something incorrectly.
Method to be called after injector creation
Method to be called after injector creation
Method to be called after successful warmup
Method to be called after successful warmup
Callback method executed after the injector is created and all lifecycle methods have fully completed.
Callback method executed after the injector is created and all lifecycle methods have fully completed.
The app is signaled as STARTED prior to the execution of this callback as all lifecycle methods have successfully completed.
This method can be used to start long-lived processes that run in separate threads from the main() thread. It is expected that you manage these threads manually, e.g., by using a com.twitter.util.FuturePool.
Any exceptions thrown in this method will result in the app exiting.
Warmup method to be called before postWarmup
Warmup method to be called before postWarmup
A com.twitter.app.App that supports injection and com.twitter.inject.TwitterModule modules.
It is not expected that you override @Lifecycle methods. If you do, take care to ensure that you call the super implementation, otherwise critical lifecycle set-up may not occur causing your application to either function improperly or outright fail.
Typically, you will only need to interact with the following methods: run -- callback executed after the injector is created and all @Lifecycle methods have completed.