The Servlet specification describes how to deploy a Web Application as a WAR file but most AppServers, GlassFish included, support deployment from an (expanded) directory. Directory deployment allows fast and easy detection of file changes and thus can lead to an improved deployment experience. Which is what Vance has been doing for NetBeans 6.1 and GlassFish v2.1 combination. Check out the description of the new functionality, first through Debug Tracing and then via Some Commentary. I belive this is available now in the corresponding nightly builts, but I need to check.

Sun Java System Web Server 7.0 update 1 is now available for download (the preview version had been available for a few months). New in this release is: • Performance and stability improvements • Out-of-box Java support for Servlets 2.5, JSP 2.1, JSF 1.2, and more • Support for Java SE 5.0 and 6 • Support for NetBeans IDE 5.5.1 • Administration interface support for FastCGI

You'll notice that the main features are Java-related. Specifically, the product is now at the Java EE 5 specification level which means that any web application that runs on GlassFish now also runs on Sun's Web Server 7.0 Update 1 (the implementation is actually taken straight from GlassFish). On the more technical side of things, you can use dependency injection in the web tier.

When released in early 2007, Web Server 7.0 enjoyed an excellent review and has been powering a whole new set of demanding web sites (including the one serving you this content). Any question, see the dedicated forum.

There is a thread at the GlassFish Forum on doing deployment-specific WebApp Configuration with a mechanism similar to that of Context.xml in Tomcat. This was at least partially addressed by RFE 2439 and, to spread the word out, Amy just described the facility in some detail. The solution in GlassFish allows global configuration as well as per-virtual host configuration. Check it out and see if this works for your needs. If not, post on the forum/ email thread.

CVR and Marina report on the Technology Preview for Sun WebServer 7.0 UR1. The main improvement in this release is the replacement of the Java Web Tier container with that of GlassFish, conforming to the JavaEE 5 specifications. This means, for example, that things like the Sun Web Developer Pack will run on it. Check CVR's announcement and download the release from here. Also thanks to Marina for the tip.

Want to know more about web hosting features in GlassFish V2? Jan Luehe will be speaking in tomorrow's (March 07, 2007) User Experience meeting. Come and listen from the "source" and feel free to give feedbacks and ask questions.

If you are using web technologies from GlassFish, you may be interested in this talk. One member of the SAP NetWeaver team spoke to me during last JavaOne about their use of one piece of GlassFish web technology. If you see this posting, please join us. Welcome!

As a GlassFish community member, you are allowed to dial into the User Experience meeting. Details on how to attend the meeting is at the UE Wiki Page. Please join the discussions and help improve GlassFish!

One of my favorite quotes says: "In theory there is no difference between theory and practice. In practice there is." (Yogi Berra or Jan_L._A._van_de_Snepscheut). In theory, we knew that we could plug in the GlassFish Web Tier into Sun's Web Server 7.0. And now Krishnamohan shows that there is practice to back it out!

This means that you will be able to run your Web Tier apps from GlassFish in your Web Server. Plus all the benefits from the Sun Web Server. Good news all along.

Thanks to CVR for the tip.

It seems quite a number of people are using GlassFish with the Apache HTTP Server, so a natural question, which Jean-Francois is asking is whether we should Formalize the Support. Your comments would be appreciated.

Added: Be sure to check the "mail thread. People are reporting success with mod_jk and mod_proxy_ajp for Apache, isapi_redirect.dll for IIS and nsapi_redirect.dll for iPlanet and Sun One web server.

Virtual hosts (or servers) are very popular and GlassFish supports them (see SJS AS 9.0 Doc Book). The support for virtual hosts has been improving in GF V2 and early in the cycle Jean-Francois explained how to Dynamically Add them. Now Jan explains the concept of a virtual server docroot and the new flexible mechanisms in the latest builds

Check Jan's blog for details. The SJS AS 9.0 docbook has a good chapter on this topic; just note that it uses the term "virtual server" instead of "virtual host" and "http-listener" instead of "connector".

The web tier of GlassFish is based on the Catalina architecture (from Tomcat 4.0) that provides a number of extension points. These extensions are implementation-specific but they are sometimes indispensable. Jean-Francois's latest entry provides an overview of the different extension points, check it out. The mechanism for adding the extensions is very easy, starting with GlassFish V2 b17, which will be part of Milestone 2, later this month.