[
https://issues.apache.org/jira/browse/PIVOT-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599502#comment-13599502
]
Steven Swor commented on PIVOT-900:
-----------------------------------
I have written a workaround for POST at
https://gist.github.com/sworisbreathing/5138350. The bulk of its code is an
overridden version of Query.execute(Method, Object) which duplicates all the
private variables to workaround the access restrictions. However, I think that
rather than incorporating this class into the source tree as-is, we could make
some changes to Query to eliminate the need to override the method.
> Allow Query responses for HTTP methods other than GET
> -----------------------------------------------------
>
> Key: PIVOT-900
> URL: https://issues.apache.org/jira/browse/PIVOT-900
> Project: Pivot
> Issue Type: Improvement
> Components: web
> Reporter: Steven Swor
>
> Currently,
> org.apache.pivot.web.Query.execute(org.apache.pivot.web.Query.Method, Object)
> is hard-coded to only deserialize an object from the response body if the
> method used is GET. However, there are situations where other methods such
> as POST are used and the server will still return a response instead of a
> redirect (such as non-RESTful web services or workarounds for large query
> strings).
> This issue is complicated because the method directly accesses several
> private-scoped variables (such as status, bytesSent, bytesReceived, and
> bytesExpected), which makes it difficult to override this method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
