Thursday, January 29, 2015

Re: WebSocket (JSR 356) + DevMode

Start here <> and follow links; the Gerrit guys had to do it as they depend on Jetty 9 too (for other purposes than websocket though; and they don't use GWTTestCase, hence HtmlUnit).
The workaround consists in using a customized gwt-dev though (where they strip the Jetty classes), so you'll have the same problem for downstream users of your library.
I think Brian's proposal (comment #10 in the issue) is the best current outcome: people who want to use WebSockets will have to deploy them in their own JSR356-aware container, and launch SDM with -launcherDir (equivalent to -noserver with DevMode, just slightly lighter). You could still create a custom Gradle task for those who use Gradle, that doesn't mean you're forcing anyone to use Gradle (people using Maven might already be running a separate servlet container anyway, "because Maven")

On Thursday, January 29, 2015 at 12:04:38 PM UTC+1, Fabien Dumay wrote:
Hey folks,

I'm implementing a nice way to use WebSocket on PWT.
Ideally I would love to be able to use it with the DevMode.
But actually the DevMode embeds Jetty 8 because of HtmlUnit. And the JSR 356 is only supported since the Jetty 9. 
Does anyone has a workaround to run DevMode or SDM with a jetty 9?

I thought to implement a new ServletContainerLauncher, but I guess that I'll face some classpath troubles.
I also imagined to create a custom gradle plugin in order to run a SDM with a -noserver option and run jetty 9 in the same task, but I do not want to force people to use gradle if they want use PWT.

Thanks for your help or any fresh ideas.



You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment