By John Clingan on Dec 10, 2009
Today we are releasing GlassFish v3 (community) and Sun GlassFish Enterprise Server v3 (commercial), following the release of Java EE 6 a few days ago. Java EE is 10 years old - nearly to the day. GlassFish v3 - the project - is 4.5 years old (although the code base for GlassFish v3 is much older).
We've come a long way with GlassFish v3, and there are quite a few "firsts" in this release (correct me if I'm over zealous - I'm living on caffeine right now):
- First Java EE 6 compatible community and commercial implementation
- First Java EE 6 Web Profile compatible community and commercial implementation
- First Java EE application server to start in seconds.
- First GlassFish distribution under 30MB (GlassFish v3 Web Profile)
- First time we managed requirements in the community
- First time we realized a wiki is less than ideal for requirements management
- First GlassFish release to document a public release schedule, milestones & all
- First time we had to update the schedule in the wiki (due to Java EE 6 release change)
- First application server that exposes a RESTful management & monitoring API
- First application server to let end users easily swap OSGi implementations
- First application server to establish a community strictly around quality testing (survey metrics). I simply cannot give this community enough kudos. The breadth of test deployments really helped improve GlassFish v3 quality.
- First application server to host dynamic language containers, such as JRuby and Jython. Web Archive packaging and servlet container not required. JRuby gem available.
- First application server with a DTrace probe (ok, a bit aggressive since it will be in beta form due to JDK 7 dependency). Learn more (here) (here).