Unable to connect via WebSocket without enabling debugger

[Marcel Dopita]

After switching to Babbler version 0.8.0, I can no longer connect to XMPP server via WebSocket. It works fine if I use ConsoleDebugger but I get following exception when setting debugger to null or when not enabling the debugger at all.

rocks.xmpp.core.session.ConnectionException: java.lang.NullPointerException
    at rocks.xmpp.core.session.XmppSession.tryConnect(XmppSession.java:373)
    at rocks.xmpp.core.session.XmppClient.connect(XmppClient.java:215)
    at rocks.xmpp.core.session.XmppSession.connect(XmppSession.java:311)
    at ...
Caused by: java.lang.NullPointerException
    at java.util.Objects.requireNonNull(Objects.java:203)
    at rocks.xmpp.websocket.net.client.WebSocketConnectionConfiguration.createWebSocketSession(WebSocketConnectionConfiguration.java:213)
    at rocks.xmpp.websocket.net.client.WebSocketConnectionConfiguration.createConnection(WebSocketConnectionConfiguration.java:162)
    at rocks.xmpp.core.session.XmppSession.tryConnect(XmppSession.java:357)
    ... 3 more

[Christian Schudt]

Make debugger optional in WebSocketConnection and NettyTcpConnection

Fixes issue #141

→ <<cset d15225cdb31c>>

[Christian Schudt]

Sorry for that.

[Christian Schudt]

Make debugger optional in WebSocketConnection and NettyTcpConnection

Fixes issue #141

→ <<cset 5daeb672d3d5>>

[Marcel Dopita]

Thank you!

[Adam Artajew]

It would be great to have also the test covering the bug along with the patch :)

[Alexandr Lukovnikov]

On Maven version 0.8.0 with bug

[Christian Schudt]

Fix version 0.8.1