jsr339-experts@jax-rs-spec.java.net

[jsr339-experts] Re: [jax-rs-spec users] Re: Re: HEADS-UP: Revise MBR selection mechanism?

From: Sergey Beryozkin <sberyozkin_at_talend.com>
Date: Thu, 24 May 2012 22:15:16 +0100

Hi Bill
On 24/05/12 18:44, Bill Burke wrote:
>
>
> On 5/24/12 12:37 PM, Sergey Beryozkin wrote:
>> That effectively makes isReadable, isWritable useless. Some
>> 'well-behaved' providers may have written in its isReadable:
>>
>> if (InputStream.class == class || isPrimitive(class)) {
>> return false;
>> }
>>
>
> Ooops! Your isReadable() forgot the possibility of ByteBuffer, byte[],
> char[] (arrays aren't primitive types), java.io.Reader, java.io.File,
> and DataSource. Not to mention any other possible custom low-level types
> somebody might want to add: i.e. Netty's or Mina's ChannelBuffer,
> Resteasy's MarshalledEntity, etc. etc. etc.
>
The chance of the resource method returning
ConcurrentHashMap representing the json array and thus falling into the
'hands' of catch-all JSON provider is very very negligible and when it
arises it would be a good idea for the developers to actually write a
custom MBR or MBW.

The chance of the users registering the custom provider supporting
multiple types is much higher IMHO

Sergey

> Bill
>


-- 
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com