New issue
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
Chat demo throws exception and only displays "Connecting.." in master #56
Comments
We can't use the sbt jetty-run task because of class loader issues which prevent socket.io from accessing jetty classes like HttpConnection.getCurrent (if that is null gives a good indication that you have duplicate jars or other class loader issues) Will check the socket-io stuff for the newer jetty version. |
What is the exact issue? Duplicate jars? It's very annoying having to deploy the war to jetty all the time when developing socketio related stuff.. |
you can also create an embedded jetty server and launch that then sbt doesn't come into play we have a sbt task that runs such an embbedded server as run task |
Confirmed that this is still broken. It used to work with
I tried upgrading to Jetty 8.0.0.M2 (socketio-java builds against this), and it says:
There has been some action in the upstream library. May be worth merging that as a preliminary step. |
As of latest snapshot of socketio-java, example now works for me in Firefox 5.0/Linux using sbt. Fails in Chromium 12.0.742.112. |
There are wicked classloader issues with Jetty and SocketIO-java. Running it outside of sbt should work. We are going to deprecate this module. Our recommendation will be to use Atmosphere as an alternative to SocketIO-Java. An example can be found at https://gist.github.com/913295. |
Upstream library is buggy and no longer supported. Our integration is still here if it works for you, but we recommend building on Atmosphere moving forward.
When opening the chat demo it gets stuck saying "Connecting...". Following exception is printed on the console.
Jetty-websocket's WebSocketFactory doesn't have an empty argument constructor in version 7.4.1.v20110513, which is defined in the project file.
Using version 7.1.6.v20100715 seems to be getting running further as it fails with NullPointerException in the SocketIOSupport handle method.
I'm using sbt jetty-run task to run the project. I noticed that the documentation says that it's not working from sbt, but it would be so much more convenient to be able to run it from there.
The text was updated successfully, but these errors were encountered: