Last November after the announcement by Oracle that no future release beyond the 3.x version of GlassFish would have support from Oracle there were a lot of doom and gloom articles about GlassFish. I tried to put my view that this probably wasn’t the end of GlassFish but time would tell.
Why we need a Strong GlassFish
As the founder of a company that is vendor independent. I think it is imperative for the Java EE community that there is a strong vibrant GlassFish server. Having GlassFish out there as a viable production open source Java EE server drives competition. Competition drives innovation in competing products. Competition drives quality in competing products. Competition drives adoption through visibility and choice. If GlassFish fades then I’m afraid that the whole of Java EE fades. There will be no competitive incentive to drive innovation in WildFly, although I’m sure the RedHat engineers wouldn’t consciously drive down innovation and quality but competition naturally keeps them lean, mean and fast. If GlassFish in the future fails to deliver a good out of the box experience for Java EE 8 and beyond due to poor quality or poor performance then future Java EE adoption as a whole is threatened. This threatens Oracle WebLogic, RedHat JBoss EAP, IBM WebSphere sales as where are the developers to choose the big beasts for production?
Optimism for the Future
Over 6 months have passed and I’ve been trying to take stock of where we are. I’ve recently hosted a community Community Q&A session with Reza Rahman and the London GlassFish User Group and organised a BOF at Devoxx UK with David Delabassee to get the community involved in what is happening with GlassFish. We’ve watched the code archives and started our own builds. Read the complete article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.