On 12/13/2011 04:13 PM, Sergey Beryozkin wrote:
> On 13/12/11 15:11, Marek Potociar wrote:
>>
>>
>> On Tue 13 Dec 2011 04:01:44 PM CET, Sergey Beryozkin wrote:
>>> Hi
>>> On 13/12/11 14:59, Bill Burke wrote:
>>>>
>>>>
>>>> On 12/13/11 9:48 AM, Marek Potociar wrote:
>>>>> Not sure we are on the same page. My question is, whether you think
>>>>> that (on the server side) the following 2 methods
>>>>> are interchangeable:
>>>>>
>>>>> request.getEntity(InputStream.class);
>>>>> request.getEntityInputStream();
>>>>>
>>>>
>>>> No we weren't on the same page :) Thanks for clarifying.
>>>>
>>>> Yes, you're right, they are interchangeable. So, yes,
>>>> getEntityInputStream() isn't needed.
>>>
>>> Will
>>>
>>> request.getEntity(Book.class);
>>>
>>> work ?
>>
>> Assuming there is a readable (e.g. in terms of applicable
>> MessageBodyReader) Book representation in the entity, the above should,
>> of course, work.
>
> And do we really want to let it happen, to get the input stream consumed by custom providers ?
Yes, I believe we do. Btw. resources may also want to consume the entity as an input stream.
> What will need to be done
> after it for the application code to get Book too ?
Interesting question. I would say that once you consume the input stream content, you either need produce a new request
and set a new entity into the Request or you the app code accessing the request may be doomed. But that's all right IMO
as long as we properly document it (filed a new issue so that we don't forget -
http://java.net/jira/browse/JAX_RS_SPEC-148 ). Our job is not to prevent any possible stupid provider implementation.
In any case, I would guess that the vast majority of stream consuming providers will be naturally implemented as reader
Handlers or MBRs.
Marek
>
> Sergey
>
>>
>> Marek
>>
>>>
>>> Cheers, Sergey
>>>
>>>>
>>>> Bill
>>>>
>>>
>>>
>