The Java EE 7 Platform Expert Group has released an Early Draft of the specification. The Appendix EE.B describe all the changes in this version. The associated Web Profile Early Draft is released as well and the Appendix WP.A.1 describe the changes from previous versions.

GlassFish has a lot to offer from Java EE 6 compliance, HA & Clustering, RESTful administration, IDE integration and many other features. However a recent blog
by Markus, a GlassFish Champion, said something different:

Ask not what GlassFish can do for you, but ask what you can do for GlassFish!

Markus explained how you can easily contribute to GlassFish without being a programming genius. The preparatory steps are simple:

• First of all: Don't be afraid!
• Prepare yourself - Get up to speed!

And then specific suggestions with cross-referenced documents:

• Review, Suggest and Add Documentation!
• Help Others - be a community hero!
• Find and File Bugs on Releases!
• Test-drive Promoted Builds and Release Candidates!
• Work with Code! Get things done!

Are you ready to contribute to GlassFish ? Read more details in Markus's blog.

Of course there can be no Java EE 7 without a GlassFish 4.0 release, its production-quality Open Source reference implementation. So expect the usual transparent development with regular promoted builds.

But before GlassFish 4.0 hits the streets, you'll be able to enjoy a 3.1.2 release, a highly compatible and improved version of the 3.1.x branch.

Of course there can be no Java EE 7 without a GlassFish 4.0 release, its production-quality Open Source reference implementation. So expect the usual transparent development with regular promoted builds.

But before GlassFish 4.0 hits the streets, you'll be able to enjoy a 3.1.2 release, a highly compatible and improved version of the 3.1.x branch.

Sathyan has recently sent an email about the recent progress made for GlassFish 3.1.2. You can read some background information about this specific release in this earlier post.

To give you a sense of where the team stands on this release, consider the following :
• First Release Candidate due out in mid-January
• Code Freeze scheduled for Dec 12th
• We're now at lucky promoted build #13• 200+ bugs already fixed

While it gets harder to get new bugs fixed every day as we approach the stabilization phase, it's not too late to provide feedback in the form of bug votes or general comments on the current promoted builds. And remember - it's never a bad idea or a bad time to submit a bug or an RFE.

Sathyan has recently sent an email about the recent progress made for GlassFish 3.1.2. You can read some background information about this specific release in this earlier post.

To give you a sense of where the team stands on this release, consider the following :
• First Release Candidate due out in mid-January
• Code Freeze scheduled for Dec 12th
• We're now at lucky promoted build #13• 200+ bugs already fixed

While it gets harder to get new bugs fixed every day as we approach the stabilization phase, it's not too late to provide feedback in the form of bug votes or general comments on the current promoted builds. And remember - it's never a bad idea or a bad time to submit a bug or an RFE.

The list of features planned for GlassFish 3.1.2 is shaping up nicely as reflected on the Wiki. This includes three types of improvements: new features, updated components and bugs fixes.

My favorite new features include DCOM node support (alternative to SSH on windows), and GMS non-multicast support. The list of updated components is also a top choice but seeing the issues you reported or the ones you care most about should be on top of your list, so make sure you vote and make it happen.

To some people who like entirely new shiny products, this may sound like a boring release. To others the "dot-dot" releases are the exciting ones given the level of stability that they reach which usually means safer large-scale deployments. Finally, remember, these are plans for GlassFish Open Source Edition and things can change (if they do, we'll keep you posted, as always).

The list of features planned for GlassFish 3.1.2 is shaping up nicely as reflected on the Wiki. This includes three types of improvements: new features, updated components and bugs fixes.

My favorite new features include DCOM node support (alternative to SSH on windows), and GMS non-multicast support. The list of updated components is also a top choice but seeing the issues you reported or the ones you care most about should be on top of your list, so make sure you vote and make it happen.

To some people who like entirely new shiny products, this may sound like a boring release. To others the "dot-dot" releases are the exciting ones given the level of stability that they reach which usually means safer large-scale deployments. Finally, remember, these are plans for GlassFish Open Source Edition and things can change (if they do, we'll keep you posted, as always).

Of all the Java EE servers, GlassFish comes out second to Resin, by a small margin, on startup time (less than two seconds), and second to TomEE on memory footprint. This shows that the innovative architecture GlassFish pioneered is still paying off as others are coming to market with similar goals and architectures.

As Antonio clearly states, this is not a benchmark but rather a way to realize how much lighter-weight almost all servers have become. Coupled with the radical simplification of Java EE 6, that's two major arguments to look into the standard Java EE platform to cover all your enterprise Java needs, that is if you're not using it already.

Of all the Java EE servers, GlassFish comes out second to Resin, by a small margin, on startup time (less than two seconds), and second to TomEE on memory footprint. This shows that the innovative architecture GlassFish pioneered is still paying off as others are coming to market with similar goals and architectures.

As Antonio clearly states, this is not a benchmark but rather a way to realize how much lighter-weight almost all servers have become. Coupled with the radical simplification of Java EE 6, that's two major arguments to look into the standard Java EE platform to cover all your enterprise Java needs, that is if you're not using it already.