GWT change Jetty version

1
votes

I want to change GWT's v. 2.7.0 embedded Jetty version v. 8.1.12.v20130726 to later jetty v. 9.2.22.v20170606, because for some reason Atmosphere websockets do not work with jetty 8 version (while it works with 9).

To make sure that it's Jetty that's causing problems for Atmosphere (and not GWT super dev mode), I deployed application.war to tomcat/Jetty servers:

  • Tomcat 7.0.79: works
  • Jetty 9.2.22.v20170606: works
  • Jetty 8.1.12.v20130726: does not work

I found a thread asking quite a similar question, GWT: Jetty version in dev mode, and I would like to expand on that. If I were to implement ServletContainerLauncher , would it not conflict with JettyLauncher ? How should I go about writting my own ServletCotainerLauncher for dev mode?

If you have any better ideas then writing my own ServletContainerLauncher, I would like to hear them.

1
gwtjettyatmosphere

1 Answers

2
votes

GWT 2.8 underwent specific modifications to make this possible - it wasn't simple, though if you review the commits, you could probably make the same changes.

Instead, I strongly urge you to consider moving to GWT 2.8.2, the latest version of GWT, released just a few days ago. The version you are using, GWT 2.7.0, is almost three years old, and has a number of other bugs that have been resolved since then.