Uses of Interface

Packages that use Lifecycle
This package builds on the beans package to add support for message sources and for the Observer design pattern, and the ability for application objects to obtain resources using a consistent API.
Annotation support for the Application Context, including JSR-250 "common" annotations, component-scanning, and Java-based metadata for creating Spring-managed objects.
Classes supporting the org.springframework.context package, such as abstract base classes for ApplicationContext implementations and a MessageSource implementation.
This package provides a facility for generic JCA message endpoint management.
Support package for declarative messaging configuration, with Java configuration and XML schema support.
This package contains the base message listener container facility.
This package provides JCA-based endpoint management for JMS message listeners.
Support classes for handling messages from simple messaging protocols (like STOMP).
Provides a "simple" message broker implementation along with an abstract base class and other supporting types such as a registry for subscriptions.
Generic support for simple messaging protocols (like STOMP).
Support for handling messages to "user" destinations (i.e.
Support classes for the open source scheduler Quartz, allowing to set up Quartz Schedulers, JobDetails and Triggers as beans in a Spring context.
Contains a variant of the application context interface for web applications, and the ContextLoaderListener that bootstraps a root web application context.
Classes supporting the org.springframework.web.context package, such as WebApplicationContext implementations and various utility classes.
Client support for WebSocket interactions.
Server-side support classes for WebSocket requests.
Client-side abstractions for WebSocket applications.
Client-side support for the Jetty WebSocket API.
Client-side classes for use with standard Jakarta WebSocket endpoints.
WebSocket integration for Spring's messaging module.
Server-side support classes including container-specific strategies for upgrading a request.
SockJS client implementation of WebSocketClient.
Support classes for SockJS including an AbstractSockJsService implementation.
Server-side support for SockJS transports including TransportHandler implementations for processing incoming requests, their session counterparts for sending messages over the various transports, and DefaultSockJsService.
TransportHandler implementation classes as well as a concrete SockJsService.