public class MultiBackgroundInitializer extends BackgroundInitializer<MultiBackgroundInitializer.MultiBackgroundInitializerResults>
BackgroundInitializer implementation that can deal with
multiple background initialization tasks.
This class has a similar purpose as
it is not limited to a single background initialization task. Rather it
manages an arbitrary number of
executes them, and waits until they are completely initialized. This is
useful for applications that have to perform multiple initialization tasks
that can run in parallel (i.e. that do not depend on each other). This class
takes care about the management of an
ExecutorService and shares it
BackgroundInitializer objects it is responsible for; so the
using application need not bother with these details.
The typical usage scenario for
MultiBackgroundInitializer is as
MultiBackgroundInitializercan create a temporary
ExecutorServiceand delete it after initialization is complete.
BackgroundInitializerobjects for the initialization tasks to be performed and add them to the
BackgroundInitializerobjects is needed call the
BackgroundInitializer.get()method. The object returned here provides access to all result objects created during initialization. It also stores information about exceptions that have occurred.
MultiBackgroundInitializer starts a special controller task that
BackgroundInitializer objects added to the instance.
Before the an initializer is started it is checked whether this initializer
already has an
ExecutorService set. If this is the case, this
ExecutorService is used for running the background task. Otherwise the
ExecutorService of this
shared with the initializer.
The easiest way of using this class is to let it deal with the management of
ExecutorService itself: If no external
provided, the class creates a temporary
ExecutorService (that is
capable of executing all background tasks in parallel) and destroys it at the
end of background processing.
Alternatively an external
ExecutorService can be provided - either at
construction time or later by calling the
BackgroundInitializer.setExternalExecutor(ExecutorService) method. In this case all
background tasks are scheduled at this external
Important note: When using an external
ExecutorService be sure that the number of threads managed by the service is
large enough. Otherwise a deadlock can happen! This is the case in the
MultiBackgroundInitializer starts a task that
starts all registered
BackgroundInitializer objects and waits for
their completion. If for instance a single threaded
is used, none of the background tasks can be executed, and the task created
MultiBackgroundInitializer waits forever.
|Modifier and Type||Class and Description|
A data class for storing the results of the background initialization performed by
|Constructor and Description|
Creates a new instance of
Creates a new instance of
|Modifier and Type||Method and Description|
Adds a new
get, getExternalExecutor, getFuture, isStarted, setExternalExecutor, start
public MultiBackgroundInitializer(java.util.concurrent.ExecutorService exec)
MultiBackgroundInitializerand initializes it with the given external
ExecutorServicefor executing the background tasks
public void addInitializer(java.lang.String name, BackgroundInitializer<?> init)
BackgroundInitializerto this object. When this
MultiBackgroundInitializeris started, the given initializer will be processed. This method must not be called after
BackgroundInitializer.start()has been invoked.
name- the name of the initializer (must not be null)
BackgroundInitializerto add (must not be null)
java.lang.IllegalArgumentException- if a required parameter is missing
start()has already been called
Copyright © 2010 - 2020 Adobe. All Rights Reserved