Should come up with plan for injection on client side
-----------------------------------------------------
Key: WINK-192
URL: https://issues.apache.org/jira/browse/WINK-192
Project: Wink
Issue Type: Bug
Components: Client
Affects Versions: 0.2
Reporter: Bryant Luk
Fix For: 0.2
I don't know if maybe we should tag this with WINK-162, but the RuntimeContext
should get set before invoking the client's request's HandlerContext chain. A
handler such as AcceptHeaderHandler can invoke a Provider's isReadable (say
wink-json-providers) before the ProvidersRegistry is put on the
RuntimeContextTLS during the readEntity/writeEntity on the client.
Should implement UriInfo and other JAX-RS interfaces to allow the widest range
of readers/writers on the client. Otherwise, if a provider is injected with
one of the Context interfaces, a NPE will occur for them as well (i.e.
wink-json-providers)
I haven't thought this all the way through but another problem is that
HttpHeaders is really intended for use on the server side only. I imagine some
of the generic provider logic for entity providers would not work correctly
(say a HttpHeaders.getAcceptableMediaTypes() is called during the writeTo() of
an entity provider).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
