Lucky number seven

JSON and more good to go for Java EE 7

Elliot Bentley

Next version of EE comes one step closer to May 13th release as the first set of feature specs get thumbs-up.

Java EE 7 came one step
closer to its May 13th release yesterday as the first set of
feature specifications were given
the thumbs-up
by its governing body.

Originally planned to be released by the end of last
year, EE 7 has suffered delays and seen both headline
cloud features
and a well-overdue
caching API
knocked back to a future EE version.

Better late than never, however; and with Java
Specification Requests (JSRs) outlining Java Message Service
, Bean
Validation 1.1
, Batch Applications for
the Java Platform
and Java API for JSON
now approved by the Executive Committee, things are
looking good for next month’s release.

The vote did not pass without some minor controversy,
however. Committee member Werner Keil abstained from voting on the
specification for batch jobs in Java, arguing that the JSR “failed
to properly point to the Spec License”

The SouJava usergroup, who voted for its inclusion,
responded that while the spec’s license is “not immediately visible
to those that come directly to the site”, its transparent
and inclusive development process made up for it.

Meanwhile, the London Java Community criticised the
Java Message Service 2.0 spec for being unambitious, given “the
innovations that have occurred in the messaging space since the
release of JMS 1.1”.

The next three weeks will see the Java EE Executive Committee
judging the remaining JSRs, including the new WebSocket API, JAX-RS
2.0 and Java EE 7 itself.

Photo by
Steven Depolo

comments powered by Disqus