Vaadin 10 brewery buddy on WildFly 12

Flow
1

I guess Vaadin 10 is not going anywhere so I might as well have a look at it.
I deployed it to a WildFly 12 instance but got deployment errors like

09:58:34,653 WARNING [org.atmosphere.container.JSR356AsyncSupport] (ServerService Thread Pool -- 69) Duplicate Servlet Mapping Path . Use org.atmosphere.container.JSR356AsyncSupport.mappingPath init-param to prevent this message 09:58:34,653 WARNING [org.atmosphere.container.JSR356AsyncSupport] (ServerService Thread Pool -- 69) Duplicate guess : javax.websocket.DeploymentException: UT003023: Multiple endpoints with the same logical mapping PathTemplate{template=true, base='/', parts=[Part{template=true, part='path0'}] } and PathTemplate{template=true, base='/', parts=[Part{template=true, part='path0'}] }

in

at com.vaadin.flow.server.communication.PushRequestHandler.initAtmosphere(PushRequestHandler.java:220) at com.vaadin.flow.server.communication.JSR356WebsocketInitializer.initAtmosphereForVaadinServlet(JSR356WebsocketInitializer.java:166) at com.vaadin.flow.server.communication.JSR356WebsocketInitializer.contextInitialized(JSR356WebsocketInitializer.java:131)

I noticed that there was some workaround with an web.xml init parameter like

org.atmosphere.container.JSR356AsyncSupport.mappingPath="/{something}"

but I noticed the web.xml doesn’t even have a web.xml. Is this still the correct workaround or is it an issue with Vaadin 10 or WildFly 12? And if it is the implicit Vaadin servlet it’s complaining about, it might break any Vaadin 10 app using the same web socket implementation(?). Works on WildFly 11, though

2

Here is about web.xml and init-parameters:
https://github.com/vaadin/flow-and-components-documentation/blob/master/documentation/advanced/tutorial-flow-runtime-configuration.asciidoc

About the websocket issues: we are currently working on websockets support in Flow.
There is an issue at least to refer:

https://github.com/vaadin/flow/issues/3251

There is a comment about Wildfly: https://github.com/vaadin/flow/issues/3251#issuecomment-366930079

I think it makes sense to create a separate issue about Widldfly which refers to the #3251 since the original issue is about Spring. It will help to track it proeprly and don’t forget once Spring websocket issue is fixed.