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]
https://jsr311.dev.java.net/issues/show_bug.cgi?id=22
[2]
https://jsr311.dev.java.net/servlets/ReadMsg?list=dev&msgNo=714
[3]
http://blogs.sun.com/sandoz/entry/jersey_client_api
[4]
https://jsr311.dev.java.net/nonav/sketches/clientapi/index.html
---
Marc Hadley <marc.hadley at sun.com>
CTO Office, Sun Microsystems.