ThreeTen, the reference implementation of JSR 310 Date and Time API, is now included in JDK 8 build 75. The Java Time API for JDK 8 is under the package java.time, moving away from the javax.time package of earlier implementations. All the Java Time classes are immutable and thread-safe, based on the ISO 8601 calendar system, the de facto world calendar following the proleptic Gregorian rules.
Adopt a JSR Program is an initiative to encourage Java User Group (JUG) members to get involved in the Java Community Process (JCP) by adopting a Java Specification Request (JSR). The team behind the Adopt-a-JSR program is hosting an online meetup on January 18. This is your opportunity to provide feedback and contribute to JCP process.
Oracle throws weight behind London JUG Adopt a JSR Program
In July, the Digital Energy unit within GE Energy Management disclosed that they were in the process of porting their Smalltalk-inspired programming language, Magik, from its own proprietary Virtual Machine, MagikSF, to the JVM. With the port now well under way, InfoQ spoke to project lead/architect George Marrows to find out more.
As JSR 342, the specification for Java EE 7, makes its way through early draft review the expert group is keen to get community feedback on a number of open issues. These include which of the new APIs should be added to the Java EE Full/Web Profile, as well as how to better align CDI with Java EE.
The results are in for the JCP 2012 elections, with the London Java Community re-elected and PaaS provider CloudBees being elected for the first time in the open vote. Following the vote, the SE/EE and ME Executive Committees will be merged into a single Executive Committee, which will start to focus on the thorny matter of IP issues.
JRuby 1.7.0 now defaults to Ruby 1.9 mode and supports almost all of 1.9's features. On recent JVM implementations that support invokedynamic, using JRuby 1.7 can increase application performance.
At JavaOne 2012 in a panel session around the future of Java EE, the audience were keen to know whether or not WADL should be a standard part of JAX-RS. Although the panel were unable to agree, the audience appeared to be more pro WADL than against. So is this a good thing or is WADL still considered unnecessary for successful REST?
Dagger is a new dependency injection framework for the Android environment. It offers a subset of features of Google Guice (some of the developers work on both projects) but focuses on a lightweight solution in order to offer better performance. Dagger also attempts to report binding errors during compile time instead of run time.
Following refactoring work carried out over the summer to simplify and refine the API, JSR 310, the long running Java Specification Request led by Stephen Colebourne to replace Java's complex date APIs, has been added to the feature list for Java 8. It is expected to arrive in January 2013’s milestone 6 release.
Brian Goetz, Java Language Architect at Oracle and specification lead for the Lambda expressions project, has announced that mailing lists for JSR 335 will be made publicly available.
In a move that is becoming rather familiar, Oracle has announced that it is looking to reduce the scope of Java EE 7 in order to keep development on track, by deferring PaaS and multi-tenancy support to Java EE 8.
The first in a new regular feature where we report on the results of the monthly meetings of the Java Community Process.
InfoQ's research initiative continues with a second question about "What Are Your Priorities for Java and the JVM?". This is part of our new service that we hope will provide you with up-to-date & bias-free community-based insight into trends & behaviors that affect enterprise software development. Unlike traditional vendor/analyst-based research, our research is based on answers provided by YOU.
With WebSockets now a W3C Candidate Recommendation and a new JSR about to start in the JCP, the question arises about how and if WebSockets work with the principles of REST? Do they compliment each other, or will WebSockets, as some people believe, divert attention away from REST and towards a new style of interaction for the Web? There is even the suggestion that WebSockets "breaks the Web".