The thing that is JSON is the "entity body". This is defined by the HTTP
standard. How you send that will depend on the other client API you're
using, so the only thing we can tell you for sure is this is the wrong
place to ask :) (No, to be fair, once you've decided what client you're
talking about, someone might well know, but clearly a list specific to the
client in question makes more sense).
BTW, you shouldn't need to create a message body reader/writer for JSON,
just use one of the provided ones. Jackson, Moxy, whatever.
HTH,
Simon
On Sat, Dec 27, 2014 at 8:05 PM, <users-request_at_jersey.java.net> wrote:
> Table of contents:
>
> 1. [Jersey] Re: Question on custom MessageBodyReader? - <zarub2k_at_gmail.com
> >
>
>
>
> ---------- Forwarded message ----------
> From: <zarub2k_at_gmail.com>
> To: users_at_jersey.java.net
> Cc:
> Date: Sat, 27 Dec 2014 03:34:22 +0000 (UTC)
> Subject: [Jersey] Re: Question on custom MessageBodyReader?
> I am using Jersey framework for my RESTful web services. Following some
> documents available in Jersey website, I developed a custom
> MessageBodyReader in-order to parse my JSON to Java object.
>
> Using JAX-RS client API, I am able to send the appropriate JSON input
> to the respective Jersey (REST) resource. Since REST is a common
> standard, how can I pass the necessary information using any other REST
> client.
>
> I am confused here because the REST resource input (JSON / Java) is not
> mapped with any one of the parameters like PathParam, QueryParam,
> FormParam or HeaderParam.
>
> If my client is like that
> Response response =
> webTarget.request().post(Entity.entity(jsonObject.toString(),
> MediaType.APPLICATION_JSON));
>
> Through which medium the JSON will be passed to the RESTful resource?
>
> Thanks,
> Tham
>
> End of digest for list users_at_jersey.java.net - Sun, 28 Dec 2014
>
>
--
Simon Roberts
Certified Professional Photographer
http://dancingcloudphotography.com
(303) 249 3613