Two key JSRs accepted in time for Java EE 7
Specifications Bean Validation 1.1 and JAX-RS 2.0 have been approved by the JCP Executive Committee.
The
final drafts of Bean Validation 1.1 and JAX-RS 2.0 have been
approved by the JCP Executive Committee, meaning they will
definitely be included in Java EE 7. Six JSRs
remain to be accepted for inclusion, including the
specification for EE 7 itself.
Key
additions to the revised Bean Validation spec, JSR 343, include
dependency injection, allowing constraint validator
implementations to get resources injected automatically;
method-level validation, which enables a “Programming by Contract”
style of coding; group conversion, which allows the targeted group
to be altered when cascading validation and improved integration
with CDI.
The original spec was released in November 2009, defining a
meta-data model and API for JavaBean validation based on
annotations. Work on an improved version began early last year,
having taken on board feedback from the first release. In March
2011, spec lead Emmanuel Bernard of Red Hat told
JAXenter that the initial version was “close to the sweet spot”
and that the JSR expert group were aiming for “an incremental
evolution [rather] than a revolution”.
The other JSR to be approved, JSR 339, is also an
update to an existing spec. Led by Santiago Pericas-Geertsen and
Marek Potociar, both Oracle employees, JAX-RS 2.0 introduces two
client APIs, both compatible with the REST style, supporting
synchronous and asynchronous response processing. Java EE
evangelist Arun Gupta of Oracle talked up the spec at a packed-out
talk JAX London earlier this year – and also took the time to
speak to
JAXenter about it on camera.
While both of these JSRs were expected to make Java EE 7, it must
come as a relief to those involved after the
high-profile delay of multitenancy features.
