Example usage for org.springframework.context Lifecycle interface-usage

List of usage examples for org.springframework.context Lifecycle interface-usage

Introduction

In this page you can find the example usage for org.springframework.context Lifecycle interface-usage.

Usage

From source file org.springframework.integration.x.rollover.file.RolloverFileMessageHandler.java

/**
 * @author Christian Tzolov (christian.tzolov@gmail.com)
 */
public class RolloverFileMessageHandler extends AbstractMessageHandler implements Lifecycle {

    private Logger logger = LoggerFactory.getLogger(RolloverFileMessageHandler.class);

From source file org.springframework.integration.xmpp.messages.XmppMessageDrivenEndpoint.java

/**
 * This component logs in as a user and forwards any messages <em>to</em> that
 * user on to downstream components. The component is an endpoint that has its
 * own lifecycle and does not need any poller
 * to work. It takes any message from a given XMPP session (as established by
 * the current {@link XMPPConnection}) and forwards the

From source file org.springframework.integration.xmpp.messages.XmppMessageSendingMessageHandler.java

/**
 * @author Josh Long
 * @author Mario Gray
 * @since 2.0
 */
public class XmppMessageSendingMessageHandler extends AbstractMessageHandler implements Lifecycle {

From source file org.springframework.integration.xmpp.presence.XmppRosterEventMessageDrivenEndpoint.java

/**
 * Describes an endpoint that is able to login as usual with a {@link org.springframework.integration.xmpp.XmppConnectionFactory} and then emit {@link org.springframework.integration.Message}s when a particular event happens to the logged in users {@link org.jivesoftware.smack.Roster}. We try
 * and generically propagate these events. In practical terms, there are a few events worth being notified of: <ul> <li>the {@link org.jivesoftware.smack.packet.Presence} of a user in the {@link org.jivesoftware.smack.Roster} has changed.</li> <li>the actual makeup of the logged-in user's {@link
 * org.jivesoftware.smack.Roster} has changed: entries added, deleted, etc.</li> </ul>
 *
 * @author Josh Long

From source file org.springframework.kafka.core.DefaultKafkaProducerFactory.java

/**
 * The {@link ProducerFactory} implementation for the {@code singleton} shared {@link Producer}
 * instance.
 * <p>
 * This implementation will produce a new {@link Producer} instance
 * for provided {@link Map} {@code configs} and optional {@link Serializer} {@code keySerializer},

From source file org.springframework.security.ldap.server.ApacheDsSSLContainer.java

public class ApacheDsSSLContainer implements InitializingBean, DisposableBean, Lifecycle, ApplicationContextAware {
    private static final Log logger = LogFactory.getLog(ApacheDsSSLContainer.class);

    final DefaultDirectoryService service;
    LdapServer server;

From source file org.springframework.statemachine.processor.StateMachineAnnotationPostProcessor.java

/**
 * A {@link BeanPostProcessor} implementation that processes method-level
 * annotations such as {@link OnTransition}.
 *
 * @author Mark Fisher
 * @author Marius Bogoevici

From source file org.springframework.web.reactive.socket.client.JettyWebSocketClient.java

/**
 * A {@link WebSocketClient} implementation for use with Jetty
 * {@link org.eclipse.jetty.websocket.client.WebSocketClient}.
 *
 * <p><strong>Note: </strong> the Jetty {@code WebSocketClient} requires
 * lifecycle management and must be started and stopped. This is automatically

From source file org.springframework.web.reactive.socket.server.support.HandshakeWebSocketService.java

/**
 * {@code WebSocketService} implementation that handles a WebSocket HTTP
 * handshake request by delegating to a {@link RequestUpgradeStrategy} which
 * is either auto-detected (no-arg constructor) from the classpath but can
 * also be explicitly configured.
 *

From source file org.springframework.web.socket.server.support.AbstractHandshakeHandler.java

/**
 * A base class for {@link HandshakeHandler} implementations, independent from the Servlet API.
 *
 * <p>Performs initial validation of the WebSocket handshake request - possibly rejecting it
 * through the appropriate HTTP status code - while also allowing its subclasses to override
 * various parts of the negotiation process (e.g. origin validation, sub-protocol negotiation,