Chat demo throws exception and only displays "Connecting.." in master about scalatra HOT 6 CLOSED

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.

from scalatra.

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..

from scalatra.

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

from scalatra.

Confirmed that this is still broken. It used to work with sbt jetty-run -- I've seen it work, and that's how I used to launch it. Log just says:

[warn] Error for /socket.io/socket.io.js

I tried upgrading to Jetty 8.0.0.M2 (socketio-java builds against this), and it says:

[warn] Error for /socket.io/websocket

There has been some action in the upstream library. May be worth merging that as a preliminary step.

from scalatra.

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.

from scalatra.

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.

from scalatra.