This project has retired. For details please refer to its Attic page.

org.apache.wink.client
Class AsyncHttpClientConnectionHandler

java.lang.Object
  org.apache.wink.client.internal.handlers.AbstractConnectionHandler
      org.apache.wink.client.AsyncHttpClientConnectionHandler

All Implemented Interfaces:

ClientHandler, ConnectionHandler

public class AsyncHttpClientConnectionHandler
extends org.apache.wink.client.internal.handlers.AbstractConnectionHandler

Extends AbstractConnectionHandler and uses AsyncHttpClient to perform HTTP request execution.

Constructor Summary

AsyncHttpClientConnectionHandler(com.ning.http.client.AsyncHttpClient asyncHttpClient)

Method Summary

ClientResponse

handle(ClientRequest request, HandlerContext context) This method is invoked for every request invocation to allow the handler to perform custom actions during the invocation.

Methods inherited from class org.apache.wink.client.internal.handlers.AbstractConnectionHandler

adaptInputStream, adaptOutputStream, writeEntity

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

AsyncHttpClientConnectionHandler

public AsyncHttpClientConnectionHandler(com.ning.http.client.AsyncHttpClient asyncHttpClient)

Method Detail

handle

public ClientResponse handle(ClientRequest request,
                             HandlerContext context)
                      throws java.lang.Exception

Description copied from interface: ClientHandler

This method is invoked for every request invocation to allow the handler to perform custom actions during the invocation. This method may be called more that once for a single request, so handlers are must be prepared to handle such situations.

Parameters:

request - a modifiable ClientRequest containing the request details

context - the handler context

Returns:

a ClientResponse instance containing the response details

Throws:

java.lang.Exception - any exception can be thrown by a handler and it will be caught by the underlying client implementation and wrapped in a ClientRuntimeException