GlassFish.next: more PaaS, more community focus

It's been more than 18 months since Oracle acquired Sun and almost as much since we put out the original GlassFish Roadmap sharing how strategic the GlassFish community and product are to Oracle. We've since executed on everything promised back then :

ALT_DESCR

• GlassFish 3.0.1, the first Oracle release
• GlassFish 3.1 with full and enhanced clustering and more
• GlassFish 3.1.1, a bug-fix release with component and platform updates (including Java SE 7)
• Started JCP expert groups : JMS 2.0, JSF 2.2, JAX-RS 2.0, EL 3.0, Servlet 3.1 and of course Java EE 7 itself, all transparently

Granted we didn't stick to the initial date for 3.1.1 and had to delay the release to address a number of customer and community concerns, which we think was the right thing to do (tm). As a consequence, with Java EE 7 on a tight schedule and GlassFish 4 set to be the associated reference implementation, we've decided to integrate the Cloud-enabling and PaaS features directly into this upcoming Java EE 7 release.

In the interim, we're looking at delivering a 3.1.2 release in the same spirit as 3.1.1, insisting on quality and stability while integrating updated versions of its various components (Jersey, Grizzly, Metro, Weld, Mojarra, etc.). Note also that more sharing of components between GlassFish and WebLogic is still very much a key goal as well as improved integration with the rest of the Fusion Middleware offering (Oracle Coherence, Oracle Access Manager, and more).

Comments:

Post a Comment:
Comments are closed for this entry.