Class WebSocketUpgradeHandler
- All Implemented Interfaces:
Handler, Handler.Container, Handler.Singleton, Request.Handler, Container, Destroyable, Dumpable, Dumpable.DumpableContainer, LifeCycle, Invocable
A Handler that may perform the upgrade from HTTP to WebSocket.
The upgrade is performed only if the request matches all the requisites
necessary for the upgrade (which vary upon the HTTP protocol version),
otherwise the request handling is forwarded to the Handler child
of this Handler.
WebSocketUpgradeHandler may be a descendant of a ContextHandler, typically as a direct child, but
possibly also further down the Handler's tree, to enable WebSocket
upgrades for that ContextHandler only.
WebSocketUpgradeHandler may be a descendant of the Server, typically as a direct child, but
possibly also further down the Handler's tree, to enable WebSocket
upgrades for possibly multiple ContextHandlers.
Typical usage:
Server server = ...;
ContextHandler context = new ContextHandler("/app");
// Create the WebSocketUpgradeHandler.
WebSocketUpgradeHandler wsHandler = WebSocketUpgradeHandler.from(server, context, container ->
{
// Map upgrade requests to "/app/ws" to an echo WebSocket endpoint.
container.addMapping("/ws", (upgradeRequest, upgradeResponse, callback) -> new EchoEndPoint());
});
// Link WebSocketUpgradeHandler as a child of ContextHandler.
context.setHandler(wsHandler);
server.setHandler(context);
server.start();
A WebSocketUpgradeHandler is associated with a ServerWebSocketContainer
that is exported as a request context attribute and can be retrieved in this way:
public boolean process(Request request)
{
// Retrieve the WebSocket container from the context attributes.
ServerWebSocketContainer container = (ServerWebSocketContainer)request.getContext().getAttribute(WebSocketContainer.class.getName());
}
-
Nested Class Summary
Nested classes/interfaces inherited from class Handler.Abstract
Handler.Abstract.NonBlockingNested classes/interfaces inherited from class AbstractLifeCycle
AbstractLifeCycle.AbstractLifeCycleListener, AbstractLifeCycle.StopExceptionNested classes/interfaces inherited from interface Container
Container.InheritedListener, Container.ListenerNested classes/interfaces inherited from interface Dumpable
Dumpable.DumpableContainerNested classes/interfaces inherited from interface Handler
Handler.Abstract, Handler.AbstractContainer, Handler.Collection, Handler.Container, Handler.Sequence, Handler.Singleton, Handler.WrapperNested classes/interfaces inherited from interface Invocable
Invocable.Callable, Invocable.InvocationType, Invocable.ReadyTask, Invocable.TaskNested classes/interfaces inherited from interface LifeCycle
LifeCycle.ListenerNested classes/interfaces inherited from interface Request.Handler
Request.Handler.AbortException -
Field Summary
Fields inherited from interface Invocable
__nonBlocking, NOOP -
Constructor Summary
ConstructorsConstructorDescriptionWebSocketUpgradeHandler(ServerWebSocketContainer container) Creates a newWebSocketUpgradeHandlerwith the givenServerWebSocketContainer.WebSocketUpgradeHandler(ServerWebSocketContainer container, Consumer<ServerWebSocketContainer> configurator) Creates a newWebSocketUpgradeHandlerwith the givenServerWebSocketContainerand the given configurator. -
Method Summary
Modifier and TypeMethodDescriptionconfigure(Consumer<ServerWebSocketContainer> configurator) Deprecated.protected voiddoStart()Starts the managed lifecycle beans in the order they were added.static WebSocketUpgradeHandlerCreates a newWebSocketUpgradeHandler.static WebSocketUpgradeHandlerfrom(Server server, Consumer<ServerWebSocketContainer> configurator) Creates a newWebSocketUpgradeHandler.static WebSocketUpgradeHandlerfrom(Server server, ContextHandler context) Creates a newWebSocketUpgradeHandler.static WebSocketUpgradeHandlerfrom(Server server, ContextHandler context, Consumer<ServerWebSocketContainer> configurator) Creates a newWebSocketUpgradeHandler.booleanInvoked to handle the passed HTTP request and response.protected booleanhandle(ServerWebSocketContainer container, Request request, Response response, Callback callback) Methods inherited from class Handler.Wrapper
getHandler, setHandlerMethods inherited from class Handler.AbstractContainer
findContainerOf, getDescendant, getDescendants, isDynamic, setDynamic, setServerMethods inherited from class Handler.Abstract
destroy, doStop, getServerMethods inherited from class ContainerLifeCycle
addBean, addBean, addEventListener, addManaged, contains, dump, dump, dump, dumpObjects, dumpStdErr, getBean, getBeans, getBeans, getContainedBeans, getContainedBeans, installBean, installBean, isAuto, isManaged, isUnmanaged, manage, removeBean, removeBeans, removeEventListener, setBeans, start, stop, unmanage, updateBean, updateBean, updateBeans, updateBeansMethods inherited from class AbstractLifeCycle
getEventListeners, getState, getState, isFailed, isRunning, isStarted, isStarting, isStopped, isStopping, setEventListeners, start, stop, toStringMethods inherited from class Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitMethods inherited from interface Container
getCachedBeans, getEventListenersMethods inherited from interface Destroyable
destroyMethods inherited from interface Dumpable.DumpableContainer
isDumpableMethods inherited from interface Handler.Container
getContainer, getDescendant, getDescendants, getDescendantsMethods inherited from interface Handler.Singleton
getHandlers, getTail, insertHandler, setHandlerMethods inherited from interface LifeCycle
addEventListener, isFailed, isRunning, isStarted, isStarting, isStopped, isStopping, removeEventListener, start, stop
-
Constructor Details
-
WebSocketUpgradeHandler
Creates a new
WebSocketUpgradeHandlerwith the givenServerWebSocketContainer.- Parameters:
container- theServerWebSocketContainerof thisWebSocketUpgradeHandler
-
WebSocketUpgradeHandler
public WebSocketUpgradeHandler(ServerWebSocketContainer container, Consumer<ServerWebSocketContainer> configurator) Creates a new
WebSocketUpgradeHandlerwith the givenServerWebSocketContainerand the given configurator.The configurator is invoked every time this
WebSocketUpgradeHandleris started, seefrom(Server, ContextHandler, Consumer).- Parameters:
container- theServerWebSocketContainerof thisWebSocketUpgradeHandlerconfigurator- aConsumerthat is called to allow theServerWebSocketContainerto be configured during the starting phase of theWebSocketUpgradeHandler
-
-
Method Details
-
from
Creates a new
WebSocketUpgradeHandler.The
WebSocketUpgradeHandleris not yet linked to the givenContextHandler, therefore the caller code must ensure that the returnedWebSocketUpgradeHandleris a descendant of the givenContextHandler.- Parameters:
server- theServerobject used to lookup common WebSocket componentscontext- theContextHandlerancestor of the returnedWebSocketUpgradeHandler- Returns:
- a new
WebSocketUpgradeHandler - See Also:
-
from
public static WebSocketUpgradeHandler from(Server server, ContextHandler context, Consumer<ServerWebSocketContainer> configurator) Creates a new
WebSocketUpgradeHandler.The
WebSocketUpgradeHandleris not yet linked to the givenContextHandler, therefore the caller code must ensure that the returnedWebSocketUpgradeHandleris a descendant of the givenContextHandler.The configurator parameter is invoked every time this
WebSocketUpgradeHandleris started, so that the endpoint configuration (removed during the stopping phase) can be re-applied upon restart.- Parameters:
server- theServerobject used to lookup common WebSocket componentscontext- theContextHandlerancestor of the returnedWebSocketUpgradeHandlerconfigurator- aConsumerthat is called to allow theServerWebSocketContainerto be configured during the starting phase of theWebSocketUpgradeHandler- Returns:
- a new
WebSocketUpgradeHandler
-
from
Creates a new
WebSocketUpgradeHandler.The
WebSocketUpgradeHandleris not yet linked to the givenServer, therefore the caller code must ensure that the returnedWebSocketUpgradeHandleris a descendant of the givenServer.- Parameters:
server- theServerobject used to lookup common WebSocket components- Returns:
- a new
WebSocketUpgradeHandler - See Also:
-
from
public static WebSocketUpgradeHandler from(Server server, Consumer<ServerWebSocketContainer> configurator) Creates a new
WebSocketUpgradeHandler.The
WebSocketUpgradeHandleris not yet linked to the givenServer, therefore the caller code must ensure that the returnedWebSocketUpgradeHandleris a descendant of the givenServer.The configurator parameter is invoked every time this
WebSocketUpgradeHandleris started, so that the endpoint configuration (removed during the stopping phase) can be re-applied upon restart.- Parameters:
server- theServerobject used to lookup common WebSocket componentsconfigurator- aConsumerthat is called to allow theServerWebSocketContainerto be configured during the starting phase of theWebSocketUpgradeHandler- Returns:
- a new
WebSocketUpgradeHandler
-
configure
@Deprecated public WebSocketUpgradeHandler configure(Consumer<ServerWebSocketContainer> configurator) Deprecated.Configures the
ServerWebSocketContainerassociated with thisWebSocketUpgradeHandler.This configuration is applied immediately and lost after a restart.
- Parameters:
configurator- the configuration code- Returns:
- this
WebSocketUpgradeHandler
-
getServerWebSocketContainer
-
doStart
Description copied from class:ContainerLifeCycleStarts the managed lifecycle beans in the order they were added.- Overrides:
doStartin classHandler.Abstract- Throws:
Exception- If there was a problem starting. Will cause a transition to FAILED state
-
handle
Description copied from interface:Request.HandlerInvoked to handle the passed HTTP request and response.
The request is accepted by returning true, then handling must be concluded by completing the passed callback. The handling may be asynchronous, i.e. this method may return true and complete the given callback later, possibly from a different thread. If this method returns false, then the callback must not be invoked and any mutation on the response reversed.
Exceptions thrown by this method may be subsequently handled by an error
Request.Handler, if present, otherwise a default HTTP 500 error is generated and the callback completed while writing the error response.The simplest implementation is:
public boolean handle(Request request, Response response, Callback callback) { callback.succeeded(); return true; }A HelloWorld implementation is:
public boolean handle(Request request, Response response, Callback callback) { response.write(true, ByteBuffer.wrap("Hello World\n".getBytes(StandardCharsets.UTF_8)), callback); return true; }- Specified by:
handlein interfaceRequest.Handler- Overrides:
handlein classHandler.Wrapper- Parameters:
request- the HTTP request to handleresponse- the HTTP response to handlecallback- the callback to complete when the handling is complete- Returns:
- True if and only if the request will be handled, a response generated and the callback eventually called. This may occur within the scope of the call to this method, or asynchronously some time later. If false is returned, then this method must not generate a response, nor complete the callback.
- Throws:
Exception- if there is a failure during the handling. Catchers cannot assume that the callback will be called and thus should attempt to complete the request as if a false had been returned.- See Also:
-
handle
protected boolean handle(ServerWebSocketContainer container, Request request, Response response, Callback callback) -
getInvocationType
- Specified by:
getInvocationTypein interfaceInvocable- Specified by:
getInvocationTypein interfaceRequest.Handler- Overrides:
getInvocationTypein classHandler.Wrapper- Returns:
- The InvocationType of this object
-
from(Server, ContextHandler, Consumer),from(Server, Consumer)orgetServerWebSocketContainer()