[
https://issues.apache.org/jira/browse/WINK-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730891#action_12730891
]
Nick Gallardo commented on WINK-86:
-----------------------------------
Ah, so I guess I see it a little differently. To me "empty incoming body"
means Content-Length == 0. So, there's no content in the stream and the
MessageBodyReader should represent that in a non-null object form.
To your point of MessageBodyReader<String>, that would be just
{code}if (contentLength == 0)
return new String();
{code}
Here's what was added to 1.1:
"See Issue 55. Clarify handling of empty message bodies for standard message
body readers. All bar JAXB will result in an empty (not null) object being
passed to the resource method. Using the JAXB entity provider will result in a
400 client error. Add description of how to override default behavior using a
custom provider."
> Empty incoming body content
> ---------------------------
>
> Key: WINK-86
> URL: https://issues.apache.org/jira/browse/WINK-86
> Project: Wink
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.1
> Reporter: Bryant Luk
> Assignee: Bryant Luk
>
> Just to discuss how should empty incoming body content be handled for each
> MessageBodyReader? Should be consistent across all readers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
