I ran into a need for MP Rest Client to honor the JAX-RS multipart annotations
Which annotations? I think multipart support is not yet in the JAX-RS spec (iiuc, it is proposed in a future version of Jakarta JAX-RS). I think most vendors support it, but using custom approaches.
Also, having browser-style cache consistency in MP Rest Client would be really nice! Automatic issuance of HEAD requests, honoring of the
Cache-Controlheader, etc. would enable certain projects to remove a bunch of manual caching.
Can you open GitHub issues for these? They sound reasonable to me.
Hey @kenfinnigan - was talking with Emily Jiang, and she was saying that by adding a hard dependency on JSON-B (which is an EE8 technology) in MP Rest Client, we should've made that a major version upgrade (2.0 instead of 1.3). The specific text in question is
Implementations must provide built-in JSON-P and JSON-B entity providers.. In 1.2, we had this text (essentially making JSON-B optional):
Implementations must provide a built-in JSON-P entity provider. If the implementation supports JSON-B, then it must also provide a built-in JSON-B entity provider.
Would you be ok with releasing a 1.3.1 reverting that language?
ClientRequestFilterthat I add to the underlying
@RegisterClientHeaders-- I suppose this means I need to finally stop using Jersey's
@ClientHeaderParam(name="MyHeader", value="someValue")- but you'd have to do that for all interfaces.