Verifies the integrety of the projects, as builds are executed immediately after a code change was detected. This plan provides no artifiacts (use a nightly build instead).
WIP: Upgrades Jetty 9.4.43.v20210629 to 10.0.15
Correct configuration of websocket compression. Compression is provided out of the box by Jetty's `permessage-deflate` extension.
Previously Openfire was registering the `permessage-deflate` extension, I assume this was attempting to enable websocket compression.
Presently, websocket compression is enabled by default in Jetty. So the correct way to control websocket compression is to disable the `permessage-deflate` extension when compression is not wanted: https://github.com/eclipse/jetty.project/issues/1341
WIP: Fix JSP compilation failure in Jetty 10.0.15
In this commit, the taglib definitions are consolidated in one place, where Jetty 10.0.5 expects to find them.
A nuisance is that with this layout, the IntelliJ IDE is no longer able to find the taglibs. This can be annoying during development, but does not introduce runtime issues.
- `WebSocketClientConnectionHandler.onConnect` assumes that `session.getRemoteAddress()` supplies an `InetSocketAddress` which might not always be true. What's the best approach in our context?
Fixed in this commit:
- Websocket server Maven artifact renamed from `websocket-server` to `websocket-jetty-server`
- `WebSocketServlet` renamed to `JettyWebSocketServlet`
- `WebSocketServletFactory` renamed to `JettyWebSocketServletFactory`
Removed WebAppLoaderFix as it is now redundant
Thanks to GregDThomas for spotting: IIRC it only worked on older versions of JRE/Jetty, so it's probably long redundant now.