[
https://issues.apache.org/jira/browse/WINK-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryant Luk reopened WINK-32:
----------------------------
In this added code, the exceptions shouldn't be caught at all to be more
consistent with other behavior in the runtime (i.e. IOException is thrown out
and could be re-mapped if response not committed) and to make sure that a 500
server error gets thrown if nothing can write out the data (there was a NPE in
the catch (Exception e) block since dataContentHandler was null so no 500s were
being thrown out):
I had to change the unit test slightly to do what I think was intended but want
to double check so I'll attach a patch here.
> Should attempt to use Data Activation Framework according to spec
> -----------------------------------------------------------------
>
> Key: WINK-32
> URL: https://issues.apache.org/jira/browse/WINK-32
> Project: Wink
> Issue Type: Bug
> Components: Server
> Reporter: Bryant Luk
> Assignee: Martin Snitkovsky
> Fix For: 0.1
>
> Attachments: WINK-32.patch
>
>
> org.apache.wink.server.internal.handlers.FlushResultHandler
> I think we need to finish this TODO eventually: =)
> // TODO: try to find a data handler using JavaBeans Activation
> Framework,
> // if found use DataSourceProvider
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
