Re: JSR311: Client API

From: Marc Hadley <Marc.Hadley_at_Sun.COM>
Date: Tue, 11 Mar 2008 14:11:23 -0400

It seems the general sentiment is to leave a client API for a
subsequent version of the API. I'm going to close issue 22 with no


On Mar 5, 2008, at 2:50 PM, Marc Hadley wrote:

> Issue 22[1] raises the question about whether we should define a
> client API as part of JAX-RS. Back in October[2] we tabled
> discussion until we'd made some progress on a client API we were
> developing for testing purposes. Paul recently blogged about the
> resulting API that has been developed in Jersey[3] and I'd like to
> revive the discussion on issue 22 now we have something concrete to
> propose. For reference I've also uploaded the javadoc[4] to the
> jsr311 project.
> The API is implemented in Jersey trunk and will be included in
> Friday's release of the 0.6 snapshot. I'd recommend getting a copy
> and playing with the classes a little to get a feel for how things
> slot together. Paul will follow up tomorrow with some additional
> worked examples.
> Note that a client API was not one of our original deliverables and
> is only being discussed in light of requests from EG members. It
> would still be an acceptable outcome (for me at least) to defer
> inclusion of a client API to a subsequent revision of the
> specification.
> We look forward to your comments.
> Thanks,
> Marc.
> [1]
> [2]
> [3]
> [4]
> ---
> Marc Hadley <marc.hadley at>
> CTO Office, Sun Microsystems.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Marc Hadley <marc.hadley at>
CTO Office, Sun Microsystems.