Wednesday Jul 30, 2014

Spotlight on GlassFish 4.1: #3 Changing the release number

'Spotlight on GlassFish 4.0.1' is a series of posts that highlights specific enhancements of the upcoming GlassFish 4.0.1 release. It could be a new feature, a fix, a behavior change, a tip, etc.

#3 Changing the release number
Originally, the upcoming release of GlassFish was going to be called GlassFish 4.0.1 as it was mostly focused on fixing issues. But based on its actual content, we decided that calling it 4.1 would make more sense and reflect more the scope of this release:
  • Support for Java SE 8 
  • Support for Java EE 7 specifications that had a Maintenance Release : CDI 1.2, WebSocket 1.1 and their respective implementations, Weld and Tyrus.
  • Updated implementations of Jersey, Grizzly, Mojarra, EclipseLink, HK2, Metro, Open MQ, EL, Derby, JavaMail, etc.
  • And some of those implementations brings additional capabilities to GlassFish (e.g. Jersey brings OAuth support)
  • Several hundreds of fixes!
  • An updated version of the Java EE 7 Tutorial
Changing a version number during a release stabilization phase is a bit tricky but we decided it was worth the effort (and the risk!). So please bare with us for as the build infrastructure is being updated to reflect this change! Everything should be back onto track in a day or two.

Tuesday Apr 22, 2014

New book: Java EE 7 with GlassFish 4 Application Server

The third edition of David Heffelfinger's Java EE book has been recently released. This updated edition is covering the latest version of the Java EE Platform, i.e. Java EE 7.

The book gives a wide introduction on the Java EE Platform and its major APIs in their latest version: JPA 2.1, EJB 3.2, JSF 2.2, CDI 1.1, JMS 2.0, JAX-RS 2.0, Beans Validation 1.1, JAX-WS 2.2, etc. The book also cover 2 of the APIs introduced in Java EE 7 : the WebSocket API and JSON-P.

So if you are new to Java EE 7 or if you have been stuck on an older version the platform, reading this book will give you a good technical overview of Java EE 7, its main APIs and they works. It will give a solid overall understanding of Java EE 7 to rapidly start. You will then be able to deep more easily in the Platform and its APIs.

NB : The book samples are using GlassFish 4 but most of the content of the book is also applicable to any other Java EE 7 application server... that's the beauty of the Java EE!

Monday Oct 07, 2013

Admin Command Framework Enhancements and Background Command Execution in Glassfish 4

The main focus of the GlassFish 4 release clearly is providing a Java EE 7 implementation that developers can use right away. However, besides Java EE 7 a small number of important changes were included in GlassFish 4. These changes include Admin Console enhancements, background execution support for long running commands, better support for REST/SSE in the administration API, log format changes, domain configuration defaults and better OSGi administration. In a detailed blog post, Bhakti Mehta describes two of these changes - Admin Command Framework enhancements to better support progress notification via SSE and support for executing admin commands in the background. We discussed some of the GlassFish 4 specific features during the JavaOne 2013 GlassFish BOF (slides below).

Martin Mares and Chandra Patel also went through the changes in detail using demos during their JavaOne technical session titled 'GlassFish 4 Overview: What’s Under the Hood?'. The presentation will be available soon on

Friday Jul 06, 2012

Jersey 2 Integrated in GlassFish 4

JAX-RS 2.0 has released Early Draft 3 and Jersey 2 (the implementation of JAX-RS 2.0) released Milestone 5.

Jakub reported that this milestone is now integrated in GlassFish 4 builds. The first integration has basic functionality working and leaves EJB, CDI, and Validation for the coming months.

Jersey 2.0 in GlassFish 4

TOTD #182 explains how to get started with creating a simple Maven-based application, deploying on GlassFish 4, and using the newly introduced Client API to test the REST endpoint.

GlassFish 4 contains Jersey 2 as the JAX-RS implementation. If you want to use Jersey 1.1 functionality, then Martin's blog provide more details on that. All JAX-RS 1.x functionality will be supported using standard APIs anyway. This workaround is only required if Jersey 1.x functionality needs to be accessed.

Here are some pointers to follow

Provide feedback on Jersey 2 to and JAX-RS specification to

Thursday Feb 09, 2012

A status on JAX-RS 2.0. Early Draft.

With the Early Draft of JAX-RS 2.0 review period closed for a little while now, here's Arun's walk through the technology's new and improved features.


The Client API seems to be a very popular feature and one that seems pretty stable at this point. Filters and Handlers is another set of new features enabling interception of requests and responses while Hypermedia, a founding principle for REST, is better supported. JAX-RS 2.0 also offers the ability to validation parameters with BeanValidation, introduces asynchronous processing (returning Future objects on the client side) and finally better connection negotiation. Read all about it here.

JAX-RS has become an important component of the Java EE platform and the cloud theme going forward is only making it even more relevant. Check out this earlier post for Marek's (co Spec Lead on JAX-RS 2.0) take on where the JSR stands.