@GwtCompatible final class ForwardingFluentFuture<V> extends FluentFuture<V>
FluentFuture
that forwards all calls to a delegate.
FluentFuture
but with extra methods, we recommend declaring your
own subclass of ListenableFuture
, complete with a method like FluentFuture.from(com.google.common.util.concurrent.ListenableFuture<V>)
to adapt an
existing ListenableFuture
, implemented atop a ForwardingListenableFuture
that
forwards to that future and adds the desired methods.Modifier and Type | Field and Description |
---|---|
private ListenableFuture<V> |
delegate |
Constructor and Description |
---|
ForwardingFluentFuture(ListenableFuture<V> delegate) |
Modifier and Type | Method and Description |
---|---|
void |
addListener(java.lang.Runnable listener,
java.util.concurrent.Executor executor)
Registers a listener to be run on the given executor.
|
boolean |
cancel(boolean mayInterruptIfRunning) |
V |
get() |
V |
get(long timeout,
java.util.concurrent.TimeUnit unit) |
boolean |
isCancelled() |
boolean |
isDone() |
addCallback, catching, catchingAsync, from, transform, transformAsync, withTimeout
private final ListenableFuture<V> delegate
ForwardingFluentFuture(ListenableFuture<V> delegate)
public void addListener(java.lang.Runnable listener, java.util.concurrent.Executor executor)
ListenableFuture
Future
's computation is complete or, if the computation is already complete, immediately.
There is no guaranteed ordering of execution of listeners, but any listener added through this method is guaranteed to be called once the computation is complete.
Exceptions thrown by a listener will be propagated up to the executor. Any exception thrown
during Executor.execute
(e.g., a RejectedExecutionException
or an exception
thrown by direct execution) will be caught and
logged.
Note: For fast, lightweight listeners that would be safe to execute in any thread, consider
MoreExecutors.directExecutor()
. Otherwise, avoid it. Heavyweight directExecutor
listeners can cause problems, and these problems can be difficult to reproduce because they
depend on timing. For example:
addListener
. That caller may be a
UI thread or other latency-sensitive thread. This can harm UI responsiveness.
Future
. That
thread may be an internal system thread such as an RPC network thread. Blocking that
thread may stall progress of the whole system. It may even cause a deadlock.
directExecutor
listeners.
This is the most general listener interface. For common operations performed using
listeners, see Futures
. For a simplified but general listener interface, see addCallback()
.
Memory consistency effects: Actions in a thread prior to adding a listener happen-before its execution begins, perhaps in another thread.
listener
- the listener to run when the computation is completeexecutor
- the executor to run the listener inpublic boolean cancel(boolean mayInterruptIfRunning)
public boolean isCancelled()
public boolean isDone()
public V get() throws java.lang.InterruptedException, java.util.concurrent.ExecutionException
java.lang.InterruptedException
java.util.concurrent.ExecutionException
public V get(long timeout, java.util.concurrent.TimeUnit unit) throws java.lang.InterruptedException, java.util.concurrent.ExecutionException, java.util.concurrent.TimeoutException
java.lang.InterruptedException
java.util.concurrent.ExecutionException
java.util.concurrent.TimeoutException