Free Report: Abandon Fish!
Migrating from GlassFish to JBoss Wildfly and TomEE
Download This Report Now:
GlassFish has come a long way, starting as a Sun Microsystems Inc. project back in mid-2005. It was based on the source code for the Sun Java System Application Server (SJAS) PE 9, which was donated to the community by Sun Microsystems along with Oracle’s donation of TopLink persistence code. The joint goal was to encourage communication between Sun & Oracle engineers and the community, enabling all developers to participate in the application server development process along with the JCP.
With this donation, developers from all over the world could access source code, nightly builds, discussion groups, and mailing lists. For the very first time in history, developers were able to meaningfully contribute to the application server development process.
With increasing uptake on Java EE technologies, GlassFish became a solid alternative for even the most attractive and performant commercial application servers. The release of GlassFish 2.1 was in more or less direct competition with Oracle’s and IBM’s WebSphere product line. But GlassFish was for free. And much faster.
Starting in November 2013, things began going downhill for GlassFish. Oracle announced that they were canceling the commercial supported version and that there will not be an Oracle GlassFish Server 4.0.
That’s why we’re going to show you how to migrate your application, DB connections & data source, plus what to do now with your Java EE implementations of EJB, CDI, JSF, JPA, and the changes you'll need to make to your repositories, IDE, Continuous Integration server and frameworks. Now go!