-
I'm migrating an application from Pax Web v7 to Pax Web v8, and I have an issue with my websocket (upgrading from Karaf 4.3 to Karaf 4.4). I don't use "war" but only the HTTP Whiteboard. In Pax Web v7, my websocket was discovered through classpath scanning - due to some issues with the websockets whiteboard. In Pax Web v8, this scanning doesn't seem to work as before, but the whiteboard seems to be fixed. :) Here are the updates I made:
After these updates, my websocket is discovered correctly and seems to be working correctly. However, I was using a configurator to manage authentication with an HTTP Header, but this configurator is no longer being called. Is there any documentation on this subject in Pax Web? How can I intercept the handshake now? Thanks! Jérémie |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Beta Was this translation helpful? Give feedback.
There's an example of whiteboard registration here: https://github.com/ops4j/org.ops4j.pax.web/blob/web-8.0.27/pax-web-itest/pax-web-itest-container/pax-web-itest-container-common/src/main/java/org/ops4j/pax/web/itest/container/websockets/AbstractWebSocketWhiteBoardIntegrationTest.java#L69
And non-whiteboard registration is by installing a bundle here: https://github.com/ops4j/org.ops4j.pax.web/blob/web-8.0.27/pax-web-itest/pax-web-itest-container/pax-web-itest-container-common/src/main/java/org/ops4j/pax/web/itest/container/websockets/AbstractWebSocketIntegrationTest.java#L65-L67 where the bundle is a WAR with scanned component: https://github.com/ops4j/org.ops4j.pax.web/blob/web-8.0.27/…