Last week, Oracle announced on their blog site the official launching of the newest version of Java Platform, Enterprise Edition – Java EE 8. The Java EE 8 also known as JSR 366 was started through the Java Community Process (JCP). The primary focus of improvements for the Java EE platform are enumerated below, details are posted on JCP website:
- Web Standards – support for HTML 5 and HTTP 2.0
- Ease of development – using CDI to improve managed bean model
- Cloud Support – enhancement of Java EE 7’s cloud support infrastructure
- Java SE 8 – use of Java SE 8 to build Java EE 8 and benefit from its features such as “repeating annotations, lambda expressions, the Date/Time API, type annotations, Completable Futures, etc.”
The following JSRs are proposed initial contents for the Java EE 8 Platform:
- Java API for JSON Binding (JSR-367) – defined as “standard binding layer (metadata & runtime) for converting Java objects to/from JSON messages”.Schedule of Final Release: Third Quarter of 2016.
- JCache (JSR-107) – “standardize in process caching of Java objects”. Final release date: March 18, 2014.
- Model View Controller (MVC)(JSR-371) – described as”a model-view controller specification for Java EE”. Schedule of Final Release: Third Quarter of 2016.
A number of additional APIs were also submitted for possible inclusion in the Java EE 8:
LiveRebel, developed by ZeroTurnaround, is a “release automation tool” which allows teams to shift to automated release process from scripted or manual releases and makes it easier for non-technical teams to start the release with just one click on a button. LiveRebel’s “one-click app releases” can deploy apps quickly and safely, has real-time tracking and monitoring of apps, and has full support for various platforms such as Java, PHP, Python, and Ruby. This product has started in 2008, however, LiveRebel’s story ended so soon.
In a statement posted last August 11 in ZeroTurnaround’s website, Jevgeni Kabanov, founder and CEO of ZeroTurnaround, declared that LiveRebel will now be discontinued. All of their active customers will be refunded and will be provided with support and help in migrating off LiveRebel until August 11, 2015 only. The company came up with the decision because their current market is not enough to sustain the product. He also thanked everyone who became a part of LiveRebel for over six years.
Here is a summary of LiveRebel’s life cycle as told by Kabanov:
- (2008): LiveRebel – Start of development
- (May 2011): LiveRebel 1.0 – First release
- (February 2012): LiveRebel 2.0 – Ability to manage any Java EE application update and choose the default strategy depending on whether the hotpatch update would be successful or not.
- (October 2012): LiveRebel 2.5 – Added support for executing custom release script
- (March 2013): LiveRebel 2.6 – Supported database and configuration changes and multi-platform releases
- (June 2013): LiveRebel 2.7 – Extended rolling update support to any web platform
The development of Java 9 is now in progress, just a few months after the general availability release of the much awaited Java 8. The OpenJDK has started the JDK 9 Project wherein they have open its repositories for “bug fixes and small enhancements only”. As stated on their Mission Statement, the goal of the project is to “produce an open-source reference implementation of the Java SE 9 Platform, to be defined by a forthcoming JSR in the Java Community Process”. Same role for JDK 9 Project will be given to the authors, committers or reviewers who contributed at least one changeset to the JDK 8 Project. JDK 9’s latest Early Access Release – build b26 is now available for download and testing.
While Java 8’s main attraction is Project Lambda, Project Jigsaw is believed to be one of the main features of Java 9. “It’s now time to switch gears and focus on creating a production-quality design and implementation suitable for JDK 9 and thence Java SE 9, as previously proposed” Mark Reinhold, Oracle’s chief Java architect stated in his blog post last July. As Reinhold mentioned, Project Jigsaw is originally meant to be included in Java 8, however, in the 3rd quarter of 2012 the Oracle team decided to "defer it from Java 8 to Java 9". Project Jigsaw is now on its Phase Two and aims to achieve the following:
- Create a modular structure wherein Java SE Platform and the JDK APIs’ will be divided into set of modules.
- Boost security and maintainability of Java SE Platform Implementations in general, and the JDK in particular;