All > Technology > Programming > Java
- The framework events of a J2EE component's existence. Each type of component has defining events that mark its transition into states in which it has varying availability for use. For example, a servlet is created and has its
init method called by its container before invocation of its service method by clients or other servlets that require its functionality. After the call of its
init method, it has the data and readiness for its intended use. The servlet's
destroy method is called by its container before the ending of its existence so that processing associated with winding up can be done and resources can be released. The
destroy methods in this example are callback methods. Similar considerations apply to the life cycle of all J2EE component types: enterprise beans, Web components (servlets or JSP pages), applets, and application clients.
- Browse Related Terms: application client, application client container, callback methods, Component, component contract, component-managed sign-on, container, Enterprise JavaBeans (EJB), life cycle (J2EE component), naming environment, Sandbox, security permission, security permission set, software reuse, Web container