I believe it's there to support async processing of one-way messages
and of async 2-way (via ws-addressing).
So... I don't think it's needed for PUT but I'm not entirely sure. The
javadoc for RequestResponseTransport is pretty giid and might help.
David
On 28/02/07, keith chapman <[EMAIL PROTECTED]> wrote:
Hi,
I was working on adding HTTP methods PUT and DELETE to HTTPWorker so that we
can get that support. This code appears at the end of handling HTTP POST.
Boolean holdResponse = (Boolean) msgContext.getProperty
(RequestResponseTransport.HOLD_RESPONSE);
if (pi.equals(InvocationResponse.SUSPEND) || (holdResponse !=
null && Boolean.TRUE.equals(holdResponse))) {
try {
((RequestResponseTransport)msgContext.getProperty(
RequestResponseTransport.TRANSPORT_CONTROL)).awaitResponse();
}
catch (InterruptedException e) {
throw new IOException("We were interrupted, so this may not
function correctly:"+ e.getMessage());
}
}
Whats the reason for having this in the POST case? It does not appear in the
GET. Was wondering whether its needed for PUT too.
Does anybody know the reason for this code?
Thanks,
Keith.
--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
