|
|
|
|
|
Harpreet has been driving the creation of a Several New WhitePapers for the Sun GlassFish Portfolio. Topics covered include: Hudson, JBoss, WebSpace Server Cloud and many more. A full list is available from the GF Portfolio Resources page. Also see the Sun.Com Resources page for whitepapers and more across all of Sun's products. All whitepapers are free but registration is required. |
|
The guys at ZeroTurnaround (makers of JRebel) have been running a survey on redeploy and restart turnaround time in Java App Servers that has >1100 responses so far. The survey's 3 questions ask about AppServer usage and redeploy and restart time. Although doing a good survey is tricky - for example, in this case the sample is self-selected (but not as bad as with the Reader's Choice), the impact of (Re)Deployment tooling/configurations is unknown and the time is estimated, not measured - I think this one is useful in calling attention to the importance of the full develop/deploy/debug cycle. GFv2 did very well and v3 is even faster! |
Jevgeni's analysis has some reasonable comments although some others seem unwarranted by the data. The most popular containers were Tomcat (29%), JBoss (25%), WLS (13%), WAS (12%) and GF (10%) (OC4J is 4%), with the caveat about self-selected samples. As a reminder of the importance of methodology, I'll point out that only 1 respondent listed Geronimo; readers may compare to that EDC Survey from Last Year.
Also note the impact of twitter and reddit in the comment thread - there are 117 comments as of this post... almost all of them very short 'heads-up' with no added value - sigh...
Last month we ran a GlassFish Adoption Survey. Our main intention was to learn about Migration patterns on the GlassFish server. Although it was a totally self-selected, unscientific, survey, we thought it would collect some interesting insights which we could then use for a more formal survey later in the year.
With those caveats, here are the highlights:
|
•
Where they migrated from (%):
•
Major reason to switch to GlassFish (1-10):
•
Biggest benefit of for-fee support (1-10):
|
Mostly what I was expecting, although I thought there would be fewer WAS and more WLS migrations. Looking forward to an improved version of the survey later in the year.
A couple of recent Red Hat announcements are relevant to the competitive landscape around the GlassFish products:
|
Red Hat announced Open Choice, which notably includes support for the Spring Framework. Also see the Press Release, Rich's note, and reactions from The Register and Rod Johnson; and, for historical/wider context, recall Oracle and Spring. |
|
The second announcement is the eXo and JBoss Partnernship, which seems quite similar to our partnership with Liferay around Sun GlassFish WebSpace Server. See Rick's post, the PR and comments at CMS Watch. |
Additional business context for all these moves include our Partnership with Liferay, the immediate release of Java EE 6 and GlassFish v3, the Oracle announcement, and even the JSR299 and JSR330 exchanges. The next few months will be interesting...
Two news pieces related to JBoss that are relevant to GF readers.
|
JBoss has announced that it has chosen Apache CXF as its main web services stack. My tally is (please send me corrections):
Metro - GlassFish, WLS, Sun's JDK, IBM's JDK, TMaxsoft, a few other JavaEE licensees.
And Sacha announces his departure from Red Hat. Enjoy the actively doing nothing part! |
|
Since I'm still in the mood for a break (I'm planning to start my holiday break early next week - and I'm not planning to spend it like last Xmas break)... a pointer to Sacha's post: SUN: (Sound?) Open Source Business Model? and John's followup: When you hit them and they smile, you know you did something right . I think Sacha is uncharacteristically off in this one. He uses the pricing for small (up to 1K employees) companies, but, equally importantly, Sun has a lot of software we can sell to these companies leveraging GlassFish (and other entry points). And that without counting on Services and Systems, which also rely and leverage Software. |
|
JBoss 5 AS 5.0 is now available as GA (announcement). The commercial version is supposed to follow "soon" (their Open Source business model is slightly different to the GlassFish model). With this announcement the most important Java EE AppServers are now compliant with JSR 244. The official Compatibility Page shows a nice 4x4 table. Below is my attempt to list them chronologically - let me know if you see mistakes. GlassFish appears twice, once for v1 and once for v2, but GlassFish v3 does not show because GFv3 prelude is not a full Java EE 5 implementation. |
• May 2006 - JavaEE 5 goes final.
• May 2006 - GlassFish v1 and
SJS AS 9.0 PE (two names - those were the bad old days).
• May 2006 -
Tmaxsoft's JEUS 6,
SAP's
NetWeaver 7.1,
Kingdee's Apsuic AppServer v5.0
• April 2007 - BEA's (now Oracle's) WebLogic 10
• May 2007 - Oracle's
Application Server 11
• June 2007 - Apache Geronimo 2 and IBM's WebSphere Community Edition
• September 2007 - GlassFish v2
• June 2008 - NEC's webOTX 8.1
• October 2008 - IBM's WebSphere 7.0
• December 2008 - RedHat's JBoss 5
Added - I updated the table with the date for Oracle's Application Server 11.
A compilation of today's news of interest:
|
|
More frameworks come with GlassFish support out-of-the-box. Seam 2.1.0 GA is out and GF support is now explicitly mentioned ([1], [2]), and Terracotta 2.7 is out, also with GlassFish support ([2]). JBoss announces a new relationship with Magnolia (website). The tip landed in my inbox as a "new JBoss portal strategy" and there seems to be some angle there as JBoss.org is switching from the JBoss portal to Magnolia Enterprise, but I think of Magnolia as mostly a CMS product rather than a portal, so will keep an eye on more details. See Announcement. NetBeans continues to get closer to NB 6.5. The community builds with the multiple localizations are now available for review and feedback - check out Masaki-san's writeup. GlassFish v3 Prelude includes support for the EJB 3.1 draft through the new update center, and Marina has modified instructions on how to Use the EJB Timer (small modification from previous instructions). And, as Android becomes more real, Google has Open Sourced it. |
My last
Hudson roundup was back in May
(hudson+adoption
).
Adoption continues to be very strong, and there are plenty of interesting links,
although I didn't try to catch up with all the backlog.
|
|
• The GlassFish Awards Program results were
Announced at Sao Paolo
with many Hudson winners.
Details on the program will be at the
GAP blog and we will recap
here • Results on two Polls: Top three sots at the ongoing Wakaleo Consulting poll are Hudson (166), Continuum (82), CruiseControl (87), while the Best Automation Tool results at WSJ SOA Reader's Choice poll are Hudson (264), Oracle's SOA Management Pack (152), IBM's Rational Functional Tester (149). • Product comparisons include Chris Read, Peter Franza, and Java Papo (really book review). Hudson looks very good in all of them. • New integrations include Integration with Sonar (the Quality Control Tool), and Integration with Windmill (the Testing Framework) • Two posts by Schenide describing integration with non-Java environments: C++, CMake and CUnit and Grails. • Several JBoss folks seem to be adopting Hudson (at least one being a GAP winner!), and the JBoss Portal folks describe a plugin that provides integration with SmartFrog. I could not find the plugin though, send me a pointer if you know where it is. And reports on two recent presentations: a CI Camp near Munich and TAE Boston 2008 |
A compilation of today's news of interest:
|
|
Alexis reports from JavaZone about his presentation on Scripting in GlassFish v3 and reports it was Standing Room Only! JavaZone seems a Nice Conference; maybe Alexis will have some pics to post?. Also from Alexis, a quick recipe for Building GFv2 from Source, in response to some questions in the mailing lists. Be sure to check the comments for clarifications on testing configurations. John recently became a committer into Grizzly. He already contributed a tutorial on Writing a Protocol using Grizzly and now has mutated that into an implementation of HTTP Chunked Transfer Coding - see his writeup on Full Duplex communication. Alex de Marco followed on the free hosting offer from OStatic and already qualified and seems very happy... and, to, give back, he provides a Quick Start Guide on his virtualized container. Release Noises Galore: SpringSource is getting ready their Apache Tomcat-based server, now under the new name ofdm Server RC2... and JBoss now has a Java EE 5-Certified JBoss 5 RC2. I guess I could have filed this under the battle of the RC2s! S2 promises a final release in 2 weeks, JBoss in around 6 - we will see... And on the big-toys front, a new version of BlackBox, the MD D20. I initially thought it would be using a longer container but it is still a 20 footer, just with different internal layout - clearly customer-driven. See the Technical Specs and the overview from On The Record. |
A compilation of today's news of interest:
|
|
Arun will be in Berlin for the Rails Conf and is already planning other visits. So far he is already planning a visit to the Berling JUG and TU; contact him if your group (or company) is interested in chatting about GlassFish et al.
Ryan has been covering the client side of GlassFish MEP:
first check out his
Mobile Client SDK
Overview,
then a
Closer look to
the MCBI API
and finally, the first part of
Developing MEP Clients.
The server side is covered by Santiago and Art,
check out
MEP Oracle has Announced WebLogic 10g R3 (InfoQ Announcement) their first release of since their acquisition of BEA. The release seems an evolution of their previous direction, with price hikes tossed in. Sacha writes about their first JavaEE 5-based GA release, JBoss 5, due in "a couple of months". Since he compares it to GlassFish, I'll note that our third JavaEE 5-based major release, GFv3 Prelude, is due in mid-October, after GFv1 - May 06 - and GFv2 - Sept 07. Also, I Will be away on a trip for the next 3 days, so don't expect any posts until Wednesday. |
|
Metro,
the
GlassFish
Web Services stack
(Metro This is not surprising: the performace of Metro is very good (see, for instance, yesterday's testimonial), its interoperability is outstanding, it's Flexible Architecture supports multiple Encodings and Transports, includes REST suport via Jersey, the licenses (GPLv2+CDDL) are very usable, it has a Growing Community and great Tool Support in NB 6.1 and is an Award-Winner. |
Metro is directly available in the enterprise-ready GlassFish v2 as well as in the modular GFv3, as well as in Sun's JDK. And, if you really insist, we even show you how to Install it on Tomcat :-)
|
Here is a new addition to our Switch series. Justin is in the process of converting from JBoss to GlassFish Server and he is going to document it in his blog. His first entry covers the two (small) issues he encountered when converting his REST-based endpoints: ordering of WARs and JDBC resource deployments. Check out From JBoss to Glassfish: Part I. I will highlight Justin's additional entries as they become available. |
I bumped into this post from David dscribing his experiences migrating his app from JBoss 4.0.4-GA to GlassFish.
|
David covers 3 issues:
• JBoss EJBQL != GF (J2EE Spec) EJBQL
Beyond this, it was a successful experience; for details, check out David's writeup. And keep the migration stories going... |
The GlassFish Awards Program (GAP)
is intended to encourage and reward innovation in the GlassFish Community.
The program's rules
(here
)
are quite loose and many types of projects will qualify.
There are US$ 175K available, for both projects and bug submissions;
check
Previous Posts for
additional commentary.
Some notes on the program:
|
• Submissions are to be sent to Gap-Submissions at GF
(Archive,
mailto).
|
We have up to 20 prizes for projects and many more for bug submissions but we have received very few submissions so far. I suspect many are waiting for the deadline, but we would much rather you submit now first and then resubmit. Don't leave money on the table!
Note! We had a configuration problem with the submission alias and it is possible that some submissions may not have been recorded properly. If you submitted, please check the alias archive, and resubmit if necessary.
