-
Notifications
You must be signed in to change notification settings - Fork 179
Warm Up
Randgalt edited this page Oct 22, 2012
·
7 revisions
In addition to the standard lifecycle annotations @PostConstruct and @PreDestroy, Governator adds: @WarmUp
Methods annotated with @WarmUp will be called in parallel (using the Java Fork-Join framework) when LifecycleManager.start() is called. Object dependencies are respected – i.e. given:
- Object A is dependent on objects B and C and all have warm up methods.
- Object A’s warm up method will not be executed until both objects B and C’s warm up methods complete.
- Objects B and C’s warm up methods will execute in parallel.
An alternate version of LifecycleManager.start() can be used to limit the amount of time allowed for warm up methods to complete.
- Home
- Getting Started
- Bootstrapping
- Lifecycle Management
- Auto Binding
- Module-Dependencies
- Warm Up
- Configuration Mapping
- Field Validation
- Lazy Singleton
- Concurrent Singleton
- Generic Binding Annotations
- LifecycleListener
- Governator Phases
- Grapher Integration
- JUnit Testing
- FAQ
- Best Practices
- Spring, PicoContainer, Etc.
- Javadoc
- End-to-End Examples