Vert.x SockJSHandler class - websocket

Question

I'm trying to build a web socket application with Vert.x, and I have found plenty of examples using the SockJSHandler, to communicate with SockJS javascript library on the front end of the application.
The examples are using version 3.5.0 of Vert.x Core and Vert.x Web, and they create an instance of the class using the method SockJSHandler.create(vertx), bridging the SockJSHandler to the Vert.x event bus through the method SockJSHandler.bridge. This last method returns the type SockJSHandler, that gets routed with router.route("/eventbusroute/*").handler(sockJsHandler()).
I'm using the latest version of Vert.x Core and Vert.x Web, the 3.8.3, and in this release the method bridge returns an instance of type Router, as stated in the documentation.
My question is: what would be the best way to route the SockJSHandler Router instance to a particular route?

Answer 1

see e.g.
https://vertx.io/docs/vertx-web/java/
Router router = Router.router(vertx);
SockJSHandler sockJSHandler = SockJSHandler.create(vertx);
BridgeOptions options = new BridgeOptions();
// mount the bridge on the router
router.mountSubRouter("/eventbus", sockJSHandler.bridge(options));
vertx/examples/service/ProcessorServiceVerticle.java
Router router = Router.router(vertx);
// Allow events for the designated addresses in/out of the event bus bridge
BridgeOptions opts = new BridgeOptions()
.addInboundPermitted(new PermittedOptions().setAddress("vertx.processor"))
.addOutboundPermitted(new PermittedOptions().setAddress("vertx.processor"));
// Create the event bus bridge and add it to the router.
router.mountSubRouter("/eventbus", SockJSHandler.create(vertx).bridge(opts));
router.route().handler(StaticHandler.create());
Code which works for me:
Router router = Router.router(vertx);
BridgeOptions options = new BridgeOptions();
options.addOutboundPermitted(new PermittedOptions().setAddressRegex(".*"));
options.addInboundPermitted(new PermittedOptions().setAddressRegex(".*"));
SockJSHandler sockJSHandler = SockJSHandler.create(vertx);
router.mountSubRouter("/eventbus", sockJSHandler.bridge(options));

Answer 2

I've found the documentation I needed in version 3.8.2 deprecations documentation.
The correct way to handle the SockJSHandler.bridge return value is to include it as a subrouter.
So, instead of using the SockJSHandler implementation like the (pre Vert.x web 3.8.2 version):
EventBus eventBus = vertx.eventBus();
Handler<BridgeEvent> handler = ...;
SockJSHandler sockJSHandler = SockJSHandler.create(vertx).bridge(options, handler);
Router router = Router.router(vertx);
router.route("/eventbusroute/*").handler(sockJSHandler);
One must include the result of the bridge method call as a subRouter like this (Vert.x web version 3.8.2+):
EventBus eventBus = vertx.eventBus();
Handler<BridgeEvent> handler = ...;
Router sockJSSubRouter = SockJSHandler.create(vertx).bridge(options, handler);
Router router = Router.router(vertx);
router.mountSubRouter("/eventbusroute", sockJSSubRouter);