From JFA: • Much simpler and better performing integration of Grizzly 1.6.1 in Jetty 6.1.6.

Webtide (the company behind Jetty) is going to participate in GlassFish v3 to help define the Web Container integration (mail thread). Prior to that, Webtide had voiced support for the soon-to-be JSP Project.

Also check other Jetty News at The Aquarium, including their participation at our first GlassFish Day, using Metro on Jetty and Jetty using our JSP implementation.

The Web services stack in GlassFish V2 uses JAX-WS 2.1 and JAXB 2.1 as the core Web services platform. WSIT extends this core by providing an implementation of key WS-* specifications. Since JavaSE 6 has Web services support through the JAX-WS 2.0 and JAXB 2.0 specifications, it allows to build basic Web services using only JavaSE 6 but does not have any of the WSIT capabilities. But now that's possible! Fabian explained how a WSIT endpoint be easily deployed using the JAX-WS Endpoint API. In a follow up post, I provide a detailed writeup with complete working code.

GlassFish Web services stack "tango" nicely on Tomcat, Jetty and JavaSE 6.

One of the principles of GlassFish is to encourage the adoption of its components, and, as part of that, we attempt to make those components portable. Vivek had already reported that JAX-WS 2.1 only depended on Servlet 2.4 and would run on Jetty (and others), and now Arun provides the specific instructions to achieve this, including the WSIT/Tango features.

Check the installation details at Arun's writeup.

Covalent recently published some benchmark results on the scalability of 3 popular Servlet containers: Tomcat 6 using the native APR, Jetty and GlassFish. The results are good for the three, but they favor TC 6 when using a very large number of connections. One danger with performance tests is that is is really hard to make accurate comparisons, despite everybodies' best intentions. For example, inside Sun I've been involved in comparisons between the Web Server and GlassFish and the results are affected by details like how many requests, what response time, what percentage of successful responses, how much memory, what tuning parameters, etc. That is why there are organizations like SPEC and benchmarks like Web2005 and SPECjAppserver (and even those have their own issues).

The Covalent piece is doing a good job in that it is dispelling the myth that Servlet containers do not scale, because it is forcing teams to provide better out of the box performance (Java SE 6 did a great job there) and because I think everybody will be more careful measuring performance. I'd expect improvements on all these fronts in the near future, in the meantime, here are some additional pointers you may want to check out...

• AB Considered Harmful
• Configuring Grizzly for Performance: Part I, Part II
• Comments from Greg W regarding Jetty in that Covalent article.

Regarding the picture, I chose Mark Twain because (a) he popularized the phrase Lies, Damned Lies, and Statistics and (b) he is such a great guy that we should have him somewhere in TheAquarium, but please do note that I am not saying that the covalent blog are lies! :-)

Jetty has accepted an invitation to attend GlassFish Day to demo their work integrating Jetty into GlassFish, which has been ongoing for several months involving Grizzly and JSP communities.

GlasssFish Day is part of CommunityOne; events include keynotes by Jonathan and Rich as well as multiple tracks, free lunch and goodies, and complimentary access to some JavaOne events next day. Attendance is free but limited and you need to register.

Jettty 6.1.0 is Now Available and it includes a new Grizzly Connector that can be used stand-alone and also provides an integration path into GlassFish.

Check Greg's Blog for a very good overview of the release, or jump directly to the full description.

Another With Grizzly news piece. Jean-Francois announces that he has Jetty working on top of Grizzly. The result can then be used directly on GlassFish and, potentially, also on other places where Jetty is being used. Stay tuned for more Grizzly-related news, in the meantime, check JFA's blog entry.

Jan reports that Jetty Has Integrated the GlassFish JSP compiler and it has nice things to say about us. The GlassFish Team is actively supporting this reuse, typical of open source projects (see DTrace in Leopard) and it factored out the JSP compiler to make it possible to Use the JDT Compiler in JSP compilations. I expect more cross-project sharing / recombinations in the future.

Added: Also check out Jan (Bartel)'s blog.