Jetty 7

[cri]

Are there any plans to move GWTs embeded Jetty to version 7? Version 6
doesn't seem that well supported anymore. For example, the Jetty WTP
Plugin (http://wiki.eclipse.org/Jetty_WTP_Plugin) doesn't support
Jetty version 6. I use Jetty for a couple of Jersey servers that my
GWT projects talk to and I use version 6 just for consistency with my
GWT projects.

Thanks for any relevant information.

[Thomas Broyer]

The embedded Jetty should only be taken for what it's for: a simple servlet container. It's only meant to run servlets, you shouldn't even care whether it's Jetty or Tomcat.

If you feel the need to be consistent, and run Jetty 6 because of that, I'd say you have a problem: you should use an external server instead, with your own software (Jetty7, or even a Jetty8 milestone, Tomcat, whatever) for your tests. You can still use the embedded Jetty for fast iterations when coding, but you should run your integration tests within the server you'd like to deploy with (and not deploy the server matching the one you're happy to easily test against).

As to your initial question, there have been attempts last summer to move to Jetty7 (mainly for the support of WebSockets IIRC) but there were issues with classloaders. John 'jat' Tamplin is an active contributor to the WebSockets protocol at the IETF, and that one seems to have finally stabilize, so GWT will probably move to Jetty7 or Jetty8 in the future… provided the classloader issues can be fixed/worked around.

[Elhanan Maayan]

can this embedded jetty be used with PersistentUnit servlet injections ?

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/a99-fbwVlS0J.

To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

[Matt Hauck]

I agree that a servlet that cares whether it runs on jetty vs. tomcat is suspect and doing something wrong. However, there are tangible differences between jetty 6 and the years that have gone on since then: i.e. updated servlet APIs. The fact that jetty 6 is stuck and an old servlet api is a strong reason to not use it anymore. I don't see why there is a hesitancy to upgrade a piece of software that is three major revisions behind and has even been end-of-life'd!

The built in jetty 6 simple doesn't work for a servlet that wants to take advantage of the newer servlet api features. Running it in an external container is an option, but makes debugging both the servlet as well as the gwt code more complicated. Why then even have am embedded server to begin with? 

It's been two years+ since this answer and gwt is still on jetty 6. Is this in plan yet to support upgrading jetty?

[Thomas Broyer]

On Friday, September 13, 2013 10:18:20 PM UTC+2, Matt Hauck wrote:

It's been two years+ since this answer and gwt is still on jetty 6. Is this in plan yet to support upgrading jetty?

Yes: https://gwt-review.googlesource.com/4323

FYI, the classloader issues were with Spring Roo, not in GWT proper, and I don't think anyone still really cares about Spring Roo + GWT integration.

[Matt Hauck]

Sweet. =)

-- 

Matt Hauck

--
You received this message because you are subscribed to a topic in the Google Groups "Google Web Toolkit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/S-oFLPXoeDM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.

To post to this group, send email to google-we...@googlegroups.com.

Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.