We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
if I assign my WebSocketProtocol
<init-param> <param-name>org.atmosphere.websocket.WebSocketProtocol</param-name> <param-value>org.atmosphere.tictactoe42a9x.JerseyWebSocketProtocol</param-value> </init-param>
when WebSocketProtocol.configure(AtmosphereConfig config) method is not called.
Please see following code:
AtmosphereFramework.initWebSocketProtocol():
protected void initWebSocketProtocol() { !!! if (webSocketProtocol != null) return; try { webSocketProtocol = (WebSocketProtocol) AtmosphereFramework.class.getClassLoader() .loadClass(webSocketProtocolClassName).newInstance(); logger.info("Installed WebSocketProtocol {} ", webSocketProtocolClassName ); } catch (Exception ex) { logger.error("Cannot load the WebSocketProtocol {}", getWebSocketProtocolClassName(), ex); webSocketProtocol = new SimpleHttpProtocol(); } !!! webSocketProtocol.configure(config); // if webSocketProtocol is not null this method will be never call }
The text was updated successfully, but these errors were encountered:
Fix for #260 [jersey][0.9.0.RC2] The WebSocketProtocol.configure() me…
8b455f5
…thod is never call if custom WebSocketProtocol is assigned in the web.xml
Fixed thanks!
Sorry, something went wrong.
eb3939a
No branches or pull requests
if I assign my WebSocketProtocol
when WebSocketProtocol.configure(AtmosphereConfig config) method is not called.
Please see following code:
AtmosphereFramework.initWebSocketProtocol():
The text was updated successfully, but these errors were encountered: