Sun has been putting a lot of resources into Glassfish, Sun's Java EE 5 open source application server (CDDL license). Sun's Java.NET bloggers are also talking about Glassfish daily. But with an open source application server market dominated by JBoss, with ObjectWeb's JonAS and IBM supporting Apache's Geronimo project, just what is the intention and status of Glassfish? Could it become the killer appserver for Java EE 5, as consultant and BEA technical director Adam Bien recently suggested? InfoQ has been been following the project and talking to the committers over the last few months to catch you up.
The initial codebase for Glassfish came from Sun's Java Application Server 8 and since then Oracle contributed TopLink Essentials to provide JPA to the tool. Glassfish is the Java EE 5 reference implementation, part of the Java EE 5 SDK, and also the core upon which Sun's middleware stack the Java Enterprise System (which includes Portal, Integration Server, etc) is being built, unlike Apache Geronimo, which although supported by IBM, is a completely separate product from IBM's commercial appserver stack. There is very little difference between GlassFish and the SJS AS other than a fancy installer and support contracts, according to Sun engineer Carla Mott - "GlassFish is intended to be a production quality app server."
Glassfish combined a number of projects, many of which have external non-Sun committers. The projects are exposed via the Java.net Maven repository The Glassfish team told InfoQ team that many of the sub-components are being widely used by the community, the most popular of which being JAXB, JSF (by all the Java EE licensees), JSP, JPA, and Grizzly (the HTTP connector). "We have a number of non-Sun committers" Eduardo said. The biggest is Oracle, but even JBoss ir creditted via their contributions to the JSF RI.
A number of people have been asking about Glassfish vs. Tomcat. Obviously, Glassfish is a full Java EE server whereas Tomcat is just a Servlet/JSP engine. Tomcat supports Servlets 2.4 whereas Glassfish supports 2.5 (allowing you to run JSF 1.2). In his 5 reasons to like Glassfish, Geertjan suggested that Glassfish's lazy initialization makes it least as light for pure servlet apps as Tomcat (a feature which Geronimo and JBoss also have). Jean Francois Arcand did a performance benchmark showing Glassfish's Grizzly NIO connector making Glassfish signficantly faster than Tomcat in 'real world' conditions. On the topic of performance, Sun will likely continue to focus on performance, particularly since it is using Glassfish for it's SpecJAppserver submissions, which by itself is a bold move that JBoss has never made in the history of the benchmark.
According to project lead Eduardo Pelegri-Lloport, Sun's strategy is to "gain ubiquity and generate revenue from services and systems." Eduardo explained that SJS AS currently comes in several versions: PE (Platform Edition - developer/entry level), SE (Standard Edition - includes clustering, failover, better manageability) and EE (Enterprise Edition - which includes a very high availabilty 5-9s feature). Although a detailed featurset for Glassfish V2 has not yet been published, Eduardo told InfoQ in June that "All of Standard Edition [clustering, failover, manageability] will be Open Source; for practical reasons some bits of EE may not yet be released as Open Source by that time-frame." Manageability was key aspect that Adam Bien blogged about, so too did Glen Smith recently. Also likely to make it into V2 is WS interoperability with Microsoft via project Tango, and server side Javascripting via project Phobos.
Could Glassfish become the next major open source application server?
The initial codebase for Glassfish came from Sun's Java Application Server 8 and since then Oracle contributed TopLink Essentials to provide JPA to the tool. Glassfish is the Java EE 5 reference implementation, part of the Java EE 5 SDK, and also the core upon which Sun's middleware stack the Java Enterprise System (which includes Portal, Integration Server, etc) is being built, unlike Apache Geronimo, which although supported by IBM, is a completely separate product from IBM's commercial appserver stack. There is very little difference between GlassFish and the SJS AS other than a fancy installer and support contracts, according to Sun engineer Carla Mott - "GlassFish is intended to be a production quality app server."
Glassfish combined a number of projects, many of which have external non-Sun committers. The projects are exposed via the Java.net Maven repository The Glassfish team told InfoQ team that many of the sub-components are being widely used by the community, the most popular of which being JAXB, JSF (by all the Java EE licensees), JSP, JPA, and Grizzly (the HTTP connector). "We have a number of non-Sun committers" Eduardo said. The biggest is Oracle, but even JBoss ir creditted via their contributions to the JSF RI.
A number of people have been asking about Glassfish vs. Tomcat. Obviously, Glassfish is a full Java EE server whereas Tomcat is just a Servlet/JSP engine. Tomcat supports Servlets 2.4 whereas Glassfish supports 2.5 (allowing you to run JSF 1.2). In his 5 reasons to like Glassfish, Geertjan suggested that Glassfish's lazy initialization makes it least as light for pure servlet apps as Tomcat (a feature which Geronimo and JBoss also have). Jean Francois Arcand did a performance benchmark showing Glassfish's Grizzly NIO connector making Glassfish signficantly faster than Tomcat in 'real world' conditions. On the topic of performance, Sun will likely continue to focus on performance, particularly since it is using Glassfish for it's SpecJAppserver submissions, which by itself is a bold move that JBoss has never made in the history of the benchmark.
According to project lead Eduardo Pelegri-Lloport, Sun's strategy is to "gain ubiquity and generate revenue from services and systems." Eduardo explained that SJS AS currently comes in several versions: PE (Platform Edition - developer/entry level), SE (Standard Edition - includes clustering, failover, better manageability) and EE (Enterprise Edition - which includes a very high availabilty 5-9s feature). Although a detailed featurset for Glassfish V2 has not yet been published, Eduardo told InfoQ in June that "All of Standard Edition [clustering, failover, manageability] will be Open Source; for practical reasons some bits of EE may not yet be released as Open Source by that time-frame." Manageability was key aspect that Adam Bien blogged about, so too did Glen Smith recently. Also likely to make it into V2 is WS interoperability with Microsoft via project Tango, and server side Javascripting via project Phobos.
Could Glassfish become the next major open source application server?
Community comments
Could Glassfish become the next major open source appserver?
by Clinton Begin,
Seems very neat
by Stefan Tilkov,
Re: Seems very neat
by Clinton Begin,
Re: Seems very neat
by Stefan Tilkov,
Re: Seems very neat
by Floyd Marinescu,
Re: Seems very neat
by anjan bacchu,
Re: Seems very neat
by Clinton Begin,
BEA and IBM have moved on
by unnisworld BLR,
Could Glassfish become the next major open source appserver?
by Clinton Begin,
Your message is awaiting moderation. Thank you for participating in the discussion.
No.
Seems very neat
by Stefan Tilkov,
Your message is awaiting moderation. Thank you for participating in the discussion.
I tried it out and expected the worst, so I was pleasantly surprised to see that it's actually working very well, has decent documentation, and overall seems to have a reasonable design. I agree with Adam that both the admin tools as well as the management console appear to be above average.
Then again, Sun doesn't exactly have a history of past software successes ...
Re: Seems very neat
by Clinton Begin,
Your message is awaiting moderation. Thank you for participating in the discussion.
Exactly. I used SunOne app server for a while, it was great compared to the rest (only WebLogic was better IMHO). It conformed well to the standards and the user interfaces were really nice. It also deployed itself easily, and web apps just worked well. It was excellent really...
...the problem is, Sun cannot sell a dingy to a drowning man. In this case, they cannot even give it to him for free. ;-)
Clinton
Re: Seems very neat
by Stefan Tilkov,
Your message is awaiting moderation. Thank you for participating in the discussion.
But maybe the approach they're taking now -- open source, optionally wrapped in a commercial package -- is going to make the difference?
Re: Seems very neat
by Floyd Marinescu,
Your message is awaiting moderation. Thank you for participating in the discussion.
Re: Seems very neat
by anjan bacchu,
Your message is awaiting moderation. Thank you for participating in the discussion.
Hi there,
What about Geronimo and JBoss ?
JBoss is what it is because of various leaders and committers -- Marc, Rickard, the geronimo guys.
It will be nice to see Sun come with deployment options for people who want to adopt it. Today, if I choose Tomcat/JBoss or IIS, I can get (some) ISP deployment options but not if I choose Glassfish.
If Netbeans/Glassfish gets a "deploy/monitor to an ISP" plugin -- similar to Ruby/Rails's capistrano and ISPs make it easy(easy for monitoring and NOT expensive) for developers to deploy applications, then Glassfish can start getting some mileage.
BR,
~A
Re: Seems very neat
by Clinton Begin,
Your message is awaiting moderation. Thank you for participating in the discussion.
No ISP in their right mind would ever support Java cheaply...at least not until we see MVM implemented...(i.e. never).
Clinton
BEA and IBM have moved on
by unnisworld BLR,
Your message is awaiting moderation. Thank you for participating in the discussion.
The leaders in Appserver market, IBM and BEA have moved on to other cash cows like Portal, SOA etc. Appserver alone is no more a hot market now. Sun needs to come up with a complete software stack which has quality, ease of use and good documentation to climb up the ladder. I sincerely hope SUN will be able to do that.