Project Coin, started by Oracle’s Joseph Darcy in 2009, is a project that determined the “set of small language changes" that should be added to JDK 7 wherein final list of features where determined on the same year. The following are the Project Coin’s features that were added to JDK 7:
- String in switch
This feature allows to switch string values, an ability similar to the existing switch on values of the primitive types.
- Automatic Resource Management
Using the Automatic Resource Management statement, resources can be closed automatically.
- Improved Type Interference for Generic Instance Creation (diamond)
The addition of limited type interference for class instance creation expression to the Java programming language will be addressed in this feature.
- Simplified Varargs Method Invocation
This will lessen the confusion on the programmers by moving the warning from the call site to the method declaration.
After four months of Build b26’s release, JDK 9’s latest Early Access Release - Build b43 is now available for download and testing. Bug fixes and small enhancements for JDK 9 repositories are still ongoing.
Meanwhile, the latest JEPs targeted to JDK 9 have been listed in the update made by JDK 9’s project site last December 12, which are as follows:
- 102: Process API Updates
Enhancements on Process API
- 143: Unified JVM Logging
A common logging system for JVM components.
- 165: Compiler Control
Various enhancements on the control of JVM compiler.
- 197: Segmented Code Cache
Code cache divided into distinct segments.
- 199: Smart Java Compilation, Phase Two
Improvements on sjavac tool.
- 201: Modular Source Code
Restructuring JDK 9’s source code into modules.
- 211: Elide Deprecation Warnings on Import Statements
Removal of “uninformative" deprecation warnings.
- 212: Resolve Lint and Doclint Warnings
To fix lint and doclint errors contained in JDK 8 and JDK 9 code base.
JSR 367 is one of the newly proposed JSRs posted in the July & August JSR Updates all of which are targeting the Java EE platform.
The JSR 367 or Java API for JSON Binding (JSON-B) specification is led by Oracle's Martin Grebac and started its review in September 2014. The growing popularity of JSON being used by most systems and layers and the release of .JSR 353 or Java API for JSON Processing (JSON-P), are the reasons why JSR 367 was born. While JSR 353 developed a standard Java API for parsing, generating, and transforming JSON data, JSR 367 was proposed to develop "a standard binding layer for converting Java objects to/from JSON messages". It is said that "JSON-B will leverage JSON-P and provide a conversion layer above it".
The proposed package name is: javax.json.bind
This JSR was presented in the recently held JavaOne Conference, an event by Oracle. Grebac posted his approved slides on their blog site. The list of advantages of having Standard API below is an excerpt from his slides:
- Switch providers easily
- Implementation complete on common ground (performance or feature-wise)
- Loss of implementation/participant is no issue for standard
- More people able to help on forums or stackoverflow, even those not using your implementation of choice
The slides also contain the JSR's description, status, goals and non-goals and other plans for the JSR.