Explore alignment with the Micro Profile Rest Client API

[glassfishrobot]

As described in the JAX-RS 2.0 JSR (http://jcp.org/en/jsr/proposalDetails?id=339)::)

The most commonly requested feature for JAX-RS 2.0 is a client API: many if not all JAX-RS implementations provide some degree of client API support. This JSR will define two client APIs, both compatible with the REST style: a low level API using a builder pattern and a higher level one leveraging the former. Common security mechanisms will also be specified. The API will not define how HTTP client implementations, such as HttpUrlConnection or the Apache HTTP client library, will plug into the API. The API will support synchronous and asynchronous response processing. WebSocket or HTTP streaming processing of responses are out of scope for this JSR and will be handled in a future revision of JAX-RS.

This issue only covers the high-level client API.

Affected Versions

[2.0]

[glassfishrobot]

@glassfishrobot Commented
Reported by robc

[glassfishrobot]

@glassfishrobot Commented
@mpotociar said:
Moving to the JAX-RS "ice-box" task log for the re-evaluation as part of a future major JAX-RS release preparations.

[glassfishrobot]

@glassfishrobot Commented
This issue was imported from java.net JIRA JAX_RS_SPEC-51

[glassfishrobot]

• Issue Imported From: https://github.com/jax-rs/api/issues/56
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @glassfishrobot

[NiklasMehner]

This ticket should be closed, since the client api has been implemented.

[mkarg]

@NiklasMehner This is not true. What the EG decided back then was to have two API levels, low level and high level. What we delivered so far is only the low level API. So this ticket still is validly open.

[chkal]

Oh, interesting. What would a high level API look like? Something like the proxy client suggested on the list?

[mkarg]

@chkal As the EG had never finished its discussion about the high level API, it is up to us to discuss it now. :-)

[spericas]

@mkarg @chkal The high-level API was intended to be like proxy client API now in MP. Not everyone liked the idea of such an API (due to tight coupling etc) and we also ran out of time and had to deliver 2.0 at the time. I think we need to look at this again as a way to align JAX-RS and MP. I'll edit the title of this one.

[derekm]

Jersey's Proxy Client API should also be reviewed: https://jersey.github.io/apidocs/latest/jersey/org/glassfish/jersey/client/proxy/package-summary.html

[asoldano]

RESTEasy: http://docs.jboss.org/resteasy/docs/3.5.0.Final/userguide/html/RESTEasy_Client_Framework.html#d4e2380

[spericas]

@asoldano Thanks for sharing the link. I noticed a sentence about interface methods only annotated with @path (akin to resource locators). On the server side, resource locators are used to programmatically bind requests to resource classes (possibly by inspecting params etc), but none of that is possible using client interfaces. So the use case here is primarily to split a potentially large interface into smaller ones?

[asoldano]

@spericas yes

[andymc12]

Closing as dupe of #598