| Skip Navigation Links | |
| Exit Print View | |
|
Oracle GlassFish Server 3.1 Application Development Guide |
Part I Development Tasks and Tools
1. Setting Up a Development Environment
Part II Developing Applications and Application Components
6. Using the Java Persistence API
7. Developing Web Applications
8. Using Enterprise JavaBeans Technology
9. Using Container-Managed Persistence
12. Developing Lifecycle Listeners
The LifecycleListener Interface
The Server Lifecycle Event Context
Considerations for Lifecycle Modules
13. Developing OSGi-enabled Java EE Applications
Part III Using Services and APIs
14. Using the JDBC API for Database Access
15. Using the Transaction Service
16. Using the Java Naming and Directory Interface
A lifecycle module listens for and performs its tasks in response to the following events in the server life cycle:
After the INIT_EVENT, the server reads the configuration, initializes built-in subsystems (such as security and logging services), and creates the containers.
After the STARTUP_EVENT, the server loads and initializes deployed applications.
After the READY_EVENT, the server is ready to service requests.
After the SHUTDOWN_EVENT, the server destroys loaded applications and stops.
After the TERMINATION_EVENT, the server closes the containers, the built-in subsystems, and the server runtime environment.
These events are defined in the LifecycleEvent class.
The lifecycle modules that listen for these events implement the LifecycleListener interface.
|