dev@jsr311.java.net

JAX-RS 2.0

From: Marc Hadley <Marc.Hadley_at_Sun.COM>
Date: Fri, 01 May 2009 16:40:44 -0400

Experts,

We are starting to think about what we'd like to include in a new JSR
for a major revision to JAX-RS. Below are the items we have so far,
please let us know if there are items you'd like to add/remove/change.

Thanks,
Marc.

(i) Client API

This has been the most frequent RFE. We can re-use a number of current
APIs, most notably message body readers and writers but will require
several new APIs too. Most JAX-RS implementations provide a client
API, we will request and survey submissions to decide on the best
approach.

(ii) Quality of source

Currently all server-provided representations are assumed to be of
equal quality for the purposes of content negotiation. We will add the
ability to specify a relative quality factor for each available
representation format.

(iii) Form data and multipart handling

Improve the handling of form data and MIME multipart data

(iv) Declarative linking

Use of annotations to automate link creation.

(v) Templating/MVC

Production of representations using standard template technologies
(e.g. JSP).

(vi) Miscellaneous

We already have a number of smaller open issues that will also be
addressed including but not limited to: improving handling of trailing
'/' in request URIs, injection of Application instance, and
enhancements to MatrixParam to control inheritance between path
segments.