On 24/05/12 17:38, Bill Burke wrote:
>
>
> On 5/24/12 12:28 PM, Sergey Beryozkin wrote:
>> I was trying to reason about it in the message you replied originally.
>> So yes, on one hand it sounds rather akward. On the other hand it does
>> not realistic that it has to be done often in real applications and as
>> show with your example such cases are easily managed by the user
>> asserting the control as opposed to relying on the assumptions.
>>
>> The proposed update looks OK to me for addressing a case without a
>> custom JSONInputStreamReader.
>>
>> I'd like to understand what happens in case of the custom provider
>> aserting in its readFrom() that it can support both Document &
>> DOMSource, where for example we also have a built in MBR<Document>
>>
>> Don't get me wrong please. IMHO we need to think a lot before making a
>> decision which can lead to a matching *custom* provider being not
>> preferred to a built in one.
>>
>
> The question I have is the Java type primary key for the match, an
> *exact* match? Or do subtypes come into play?
MBR<SuperBook> wins over MBR<Book>, where SuperBook extends Book.
Cheers, Sergey
>