[
https://issues.apache.org/jira/browse/WINK-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Elman resolved WINK-31.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.1
Assignee: (was: Michael Elman)
This Issue should be fixed after revision 790466.
We may still want to discuss if we want to continue using the exceptions
handling policy we had or to change it.
> MessageBodyReader.readFrom throws IOException is turned into
> WebApplicationException but might just need to propagate out?
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: WINK-31
> URL: https://issues.apache.org/jira/browse/WINK-31
> Project: Wink
> Issue Type: Bug
> Components: Common, Server
> Reporter: Bryant Luk
> Priority: Minor
> Fix For: 0.1
>
>
> In the event that a MessageBodyReader.readFrom were to throw an IOException,
> I believe that the IOException should propagate out "untouched" (i.e. don't
> turn it into a WebApplicationException). This allows the error handling
> chain (or the underlying container's error handling capabilities) to map it
> like a IOException instead of having someone doing a getCause() on the
> WebApplicationException.
> Around line 135 in wink-server/src/main/java
> org.apache.wink.server.internal.registry.ServerInjectableFactory is where the
> change would need to start to be made.
> I'm open for debate on this one since the spec is vague and unclear on this
> behavior.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
