Re: [Resteasy-developers] @Produces/@Consumes required for clients?

[Peter M. <res...@pm...>]

BTW, created https://issues.jboss.org/browse/RESTEASY-615 for this.

-pete

On Mon, Oct 17, 2011 at 9:41 AM, Peter Murray <res...@pm...> wrote:

> My previous email was not clear - I mean to suggest that perhaps there is
> an *option* for a default MediaType that the proxy-creator can specify.
>  Maybe like this:
>
> ProxyBuilder.build(MyInterface.class, "http://localhost:8080/foo
> ").serverProduces(MediaType.APPLICATION_JSON).serverConsumes(MediaType.APPLICATION_JSON).now();
>
> or, as a convenience:
>
> ProxyBuilder.build(MyInterface.class, "http://localhost:8080/foo
> ").serverMediaType(MediaType.APPLICATION_JSON).now();
>
> The default value for these would be null (not specified) so the behavior
> would mimic exactly the current behavior (i.e. require an @Produces /
> @Consumes anno).  Only if the user of the proxy specified a default would it
> be used.
>
> Best,
>
> pete
>
> On Mon, Oct 17, 2011 at 8:43 AM, Bill Burke <bb...@re...> wrote:
>
>> It should probably mirror the server-side default which is an octet
>> stream I believe.
>>
>> On 10/17/11 8:41 AM, Peter Murray wrote:
>> > Is it the case that proxy clients currently require methods exchanging
>> > body content be annotated with @Produces and/or @Consumes?  It appears
>> > that the client uses those annotations exclusively to determine how to
>> > encode / decode arguments and return values.
>> >
>> > Please correct me if I am wrong here, but it seems to me that the
>> > available representation (json, xml, etc) to clients is an orthogonal
>> > concern to the method definition except in cases where the method itself
>> > is rendering a specific type directly in the implementation.  The
>> > availability of MessageBodyReader/Writer implementations in the JAX/RS
>> > classpath at runtime is what determines what types the server system can
>> > supply.
>> >
>> > Would it make sense, therefore, for the client proxies to have available
>> > a default MediaType for sending and one for receiving that can be
>> > configured when generating the proxy?  Then, in cases where the method
>> > is not annotated, the client would have a type to fall back on.
>> >
>> > Best,
>> >
>> > --
>> > -pete
>> > peter m. murray
>> > pe...@pm... <mailto:pe...@pm...>
>> >
>> >
>> >
>> ------------------------------------------------------------------------------
>> > All the data continuously generated in your IT infrastructure contains a
>> > definitive record of customers, application performance, security
>> > threats, fraudulent activity and more. Splunk takes this data and makes
>> > sense of it. Business sense. IT sense. Common sense.
>> > http://p.sf.net/sfu/splunk-d2d-oct
>> >
>> >
>> >
>> > _______________________________________________
>> > Resteasy-developers mailing list
>> > Res...@li...
>> > https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>>
>> --
>> Bill Burke
>> JBoss, a division of Red Hat
>> http://bill.burkecentral.com
>>
>>
>> ------------------------------------------------------------------------------
>> All the data continuously generated in your IT infrastructure contains a
>> definitive record of customers, application performance, security
>> threats, fraudulent activity and more. Splunk takes this data and makes
>> sense of it. Business sense. IT sense. Common sense.
>> http://p.sf.net/sfu/splunk-d2d-oct
>> _______________________________________________
>> Resteasy-developers mailing list
>> Res...@li...
>> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>>
>
>