InfoQ Homepage JCP Standards Content on InfoQ
-
WebSockets versus REST?
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".
-
Azul Systems and Twitter Elected to the JCP Executive Committee, VMware No Longer Represented
Twitter and Azul Systems have been elected to serve on the JCP Executive Committee for Java SE/EE, on voting percentages of 32% and 19% respectively. Both firms have also joined the OpenJDK project. VMware is no longer represented.
-
Apache TomEE Certified Web Profile Compatible
Yesterday at JavaOne, the Apache Foundation announced the availability of the Apache TomEE stack, a Java EE 6 Web Profile Compatible Implementation.
-
JSR-107, JCache: Alive and Going to be Part of Java EE 7
Distributed caching is the tip of the spear for performance, yet Java does not have a standard API. JSR-107 has gained some notoriety over the years because its old yet not done. Given the increased demand for caching, it seems JSR-107 will finally see the light of day, and be part of Java EE 7. InfoQ caught up with Greg Luck, JSR-107 specification and Ehcache lead developer to discuss.
-
Looking Past Lambda
A view to the future after project Lambda has been shared on the Lambda-Dev mailing list, hinting at a more functional Java in future with the possibility of functional types post Java 8.
-
JCP.next Public Review
Oracle have announced a public review for JCP.next, which aims to increase transparency by forcing discussions to happen in the open and use publicly viewable issue trackers. However, it does not address the key issues with the JSPA which led to complaints about the JCP earlier this year.
-
Java7 Hotspot Loop Bug Details
Last week, Oracle released Java7 to great acclaim. However, an issue identified by the Apache Lucene project pointed to a specific hotspot optimisation bug which kicks in when a loop is executed more than 10,000 times. How serious is this issue, and does it warrant the kind of negative press that has been played out over the last few days?
-
JavaSE 7 JSR Approved Despite Division
Oracle has announced that the JavaSE 7 governing JSR (336) has passed the public review ballot. Google voted against the vote, Werner Keil abstained, and no vote was received from Credit Suisse. Many others adding their concerns regarding the ongoing licensing dispute between Sun/Oracle and Apache.
-
Oracle Proposes Improvements to JCP
Yesterday, Oracle announced the start of JSR.next, also known as JSR 348, to upgrade the current JCP to force more openness and transparency. Read on to find out more.
-
IBM Releases New 64-bit Java SDK for z/OS
IBM has released two new Java 6 SDKs based on its J9 VM, to take advantage of enhancements to z/OS Java security and the new z196 instructions.
-
Oracle's Java EE 7 Plans Include Adding Cloud and HTML5 Support to the Platform
Oracle filed the umbrella JSR for Java EE 7 last week, and the specification has now passed the initial review ballot stage. The overarching themes are emerging web technologies, cloud computing, and continued ease of use improvements including an overhaul to the JMS API. Elsewhere, JPA is scheduled to receive attention, and Oracle is talking about plans to revive the long dormant JCACHE JSR.
-
Oracle Nominates SouJava to Replace Apache on the JCP EC
Oracle has announced plans to nominate one of the world's largest Java user groups, SouJava, to the JCP Executive Committee
-
InvokeDynamic Updates in OpenJDK
The OpenJDK builds recently started to include an updated version of the JSR 292 API, which, whilst not yet final, gives a good indication as to how the JSR is shaping up.
-
Apache Software Foundation Resigns from JCP
The Apache Software Foundation announced their resignation from both the JCP Executive Committee as well as the JCP as a whole. They follow recent departures such as Doug Lea in October, who said “I believe that the JCP is no longer a credible specification and standards body”, as well as more recently Tim Peierls, who voted against the Java SE JSRs.
-
JSRs for Java 7 and Java 8 Approved
The results of the recent Java JSRs are in, and all have passed with all but Apache voting consistently against them. Google and Tim Peierls voted against the Java SE 7 and Java SE 8 JSRs, supporting the ongoing licensing issues and field-of-use restrictions for the TCK.