DPI for ServerEndpoints in Jetty and Java SE

1 minute read

I am currently working on some small private Java SE project that uses WebSockets. What I wanted, was to inject an application-scoped instance into my ServerEnpoint:

@ServerEndpoint(value = "/")
public class ServerEndpoint {
  private ISomeDependentComponent someDependentComponent;
  public ServerEndpoint(ISomeDependentComponent someDependentComponent) {
    this.someDependentComponent = someDependentComponent;

I started using Tyrus. I was, however, a little disappointed when I realized that I cannot inject application-scoped instances into my ServerEndpoint. One can control the instantiation of a ServerEndpoint with a configurator like this, or use Weld for CDI in Java SE environment:

@ServerEndpoint(value = "/", configurator=ServerEndpointConfigurator.class)
public class ServerEndpoint {...}
public class ServerEndpointConfigurator extends ServerEndpointConfig.Configurator {

    public <T> T getEndpointInstance(Clas<T> endpointClass) throws InstantiationException {
        return (T)new ServerEndpoint(new SomeDependentComponent());

But again, one does not have any control over the instantiation of the ServerEndpointConfigurator. So yes, one can inject something but only in case you know what instance to inject at compile time, or one introduces some other fancy mechanism like a static provider.

Since I lost hope in finding a proper solution for Tyrus and didn’t want to use Weld (total overkill), I decided to give Jetty a try.

After some time digging around in Jetty’s code, I finally found some solution.

We just need some ServerEndpointConfig:

public class ServerEndpointInstanceFactory<T> implements ServerEndpointConfig {

  private final Function<Class<T>, T> endpointFactory;
  private final Class<T> clazz;

  public ServerEndpointBaseConfigInstanceFactory(Class<T> clazz, Function<Class<T>, T> endpointFactory) {
    this.endpointFactory = endpointFactory;
    this.clazz = clazz;
  public Configurator getConfigurator() {
    return new Configurator() {
      public <E> E getEndpointInstance(Class<E> endpointClass) throws InstantiationException {
        return (E) endpointFactory.apply((Class<T>) endpointClass);
  public Class<?> getEndpointClass() {
    return clazz;
  //ommitted other methods; they just return null

This ServerEndpointConfig will serve as a base config for the actual AnnotatedServerEndpointConfig selected by Jetty (I checked with annotated ServerEndpoints, only. I am not sure if this still works that way if your ServerEndpoint extends Endpoint.). The AnnotatedServerEndpointConfig will pick the values either from our base config or the annotated ServerEndpoint.

Since we are now able to provide an instance of an additional ServerEndpointConfig. We are now able to indirectly inject instances into the ServerEndpoint like this (line 12 and 13).

Server server = new Server();
ServerConnector connector = new ServerConnector(server);

ServletContextHandler context = new ServletContextHandler(ServletContextHandler.SESSIONS);

ServerContainer wscontainer;
wscontainer = WebSocketServerContainerInitializer.configureContext(context);
wscontainer.addEndpoint(new ServerEndpointBaseConfigInstanceFactory<ServerEndpoint>(ServerEndpoint.class,
  t -> new ServerEndpoint((condition) ? new SomeDependentComponentA() : new SomeDependentComponentB())));