Resources such as layers, maps, portal items, tasks, and so on, commonly rely on remote services or datasets on disk to initialize their state. The nature of accessing such data requires the resources to initialize their state asynchronously. The loadable design pattern unifies the behavior that different resources use to load metadata asynchronously, and resources that adopt this pattern are referred to as "loadable." The pattern also provides a mechanism to retry if previous attempts to load failed so that you can properly handle and recover from exceptional circumstances such as network outages or service interruption. Loadable resources appropriately handle concurrent and repeated requests to load in order to accommodate the common practice of sharing the same resource instance among various parts of an application, and also permit cancellation so that you can cancel loading a resource, for example, if the service is slow to respond. Finally, loadable resources provide information about their initialization status through explicit states that can be inspected and monitored.
Classes that conform to the loadable pattern implement the Loadable interface.
Load status
The get the state of the loadable resource. Four states are possible:
NOT—the resource has not been asked to load its metadata and its state isn't properly initialized yet._LOADED LOADING—the resource is in the process of loading its metadata asynchronously.FAILED—the resource failed to load its metadata (for example, due to network outage, or the operation was canceled, and so on.) The error encountered is available from the_TO _LOAD getmethod.Load Error LOADED—the resource successfully loaded its metadata and its state is properly initialized.
The following state transitions represent the stages that a loadable resource goes through.
The Loadable interface includes listeners that make it easy to monitor the status of loadable resources, display progress, and take action when the state changes.
Loading
A resource starts loading its metadata asynchronously when
load is invoked. At that time, the load status changes from NOT to LOADING. When the asynchronous operation completes, the callback is invoked. If the operation encounters an error, the error argument in the callback is populated, and load status is set to FAILED. If the operation completes successfully, the error argument is null and the load status is set to LOADED, which means the resource has finished loading its metadata and is now properly initialized.
Many times, the same resource instance is shared by different parts of the application. For example, a legend component and a table of contents component may have access to the same layer, and they both may want to access the layer's properties to populate their UI. Or the same portal instance may be shared across the application to display the user's items and groups in different parts of the application. In order to accommodate this type of application development pattern and make things simple for you, load supports multiple "listeners". It can be called concurrently and repeatedly, but only one attempt is ever made to load the metadata. If a load operation is already in progress (LOADING state) when load is called, it simply piggy-backs on the outstanding operation and the callback is enqueued to be invoked when that operation completes. If the operation has already completed (LOADED or FAILED state) when load is called, the callback is immediately invoked with the past result of the operation, be it success or failure, and the state remains unchanged. This makes it safe for you to liberally invoke load on a loadable resource, without having to check if the resource is already loaded or not, and without worrying that it will make unnecessary network requests every time.
If a resource has failed to load, calling load on it subsequently will not change its state. The callback will be invoked immediately with the past load error. In order to retry loading the resource, you must use retry instead. The advantage of this approach is that if, hypothetically, load were to retry loading a failed resource, an app could easily end up making many asynchronous requests to load the same resource just because it shared the same resource instance in different parts of the application and each part tried to load the resource without first checking if it was already loading. This pattern allows load to be invoked indiscriminately without worrying that it might add overhead, and makes retrying a separate and explicit scenario using retry.
Retry loading
A resource retries to load its metadata when retry is invoked, but only if it previously failed to load (FAILED state) or wasn't loaded to begin with (NOT state). The resource transitions to the LOADING state and makes a new attempt to fetch its metadata. The callback is invoked when the asynchronous operation completes.
If the resource has already fetched its metadata and has initialized its state (LOADED state), retry doesn't do anything. Instead, retry immediately calls the callback with the past result and the state of the object remains unchanged. The object's metadata isn't fetched again.
If an asynchronous operation is already in progress (LOADING state) when retry is called, it simply piggy-backs on the outstanding operation and the callback is enqueued to be invoked when that operation completes.
The main use case for this method is if the loadable failed to load previously, for example, due to network outage or service interruption. It is not meant to refresh the metadata for an already loaded resource which should instead be accomplished by creating a new instance of the loadable resource.
Cancel loading
A resource cancels any outstanding asynchronous operation to load its metadata when cancel is invoked and it transitions from LOADING to FAILED state. The get information that reflects that operation was canceled.
This method should be used carefully because all enqueued callbacks for that resource instance will get invoked with an error stating that the operation was canceled. Thus, one component in the application can cancel the load initiated by other components when sharing the same resource instance.
The cancel method does nothing if the resource is not in LOADING state.
Conveniences
Cascading load dependencies
It is common for a loadable resource to depend on loading other loadable resources to properly initialize its state. For example, a portal item cannot finish loading until its parent portal finishes loading. A feature layer cannot be loaded until its feature service table is first loaded. This situation is referred to as a load dependency.
Loadable operations invoked on any resource transparently cascade through its dependency graph. This helps simplify using loadable resources and puts the responsibility on the resource to correctly establish and manage its load dependencies.
The following code example shows how this cascading behavior leads to concise code. Loading the map causes the portal item to begin loading, which in turn initiates loading its portal. You do not have to load each one of them explicitly.
// Create a Map which is loaded from a webmap.
UserCredential creds = new UserCredential("myuser", "password");
Portal portal = new Portal("http://myportal/");
portal.setCredential(creds);
final PortalItem portalItem = new PortalItem(portal, "5cdcac1d6d814b82a48453d3e3876fd1");
// Make a map from portal item.
ArcGISMap map = new ArcGISMap(portalItem);
// Load the map.
map.loadAsync();
// Listen to when it is loaded.
map.addDoneLoadingListener(() -> {
if(map.getLoadStatus() == LoadStatus.LOADED) {
System.out.println("map loaded");
}
});
It is possible that dependencies may fail to load. Some dependencies might be critical without which the initiating resource cannot load successfully, for example, a portal item's dependency on its portal. If a failure is encountered while loading such a dependency, that error would bubble up to the resource that initiated the load cycle, which would also fail to load. Furthermore, retrying to load that resource would automatically retry loading the failed dependency. Other load dependencies may be incidental, such as a map's dependency on one of its operational layers, and the resource may be able to load successfully even if one of its dependency fails to load.
Overriding state before initialization
A loadable resource's state is not properly initialized until it has finished loading. Accessing properties of the resource before the resource is loaded could return null or uninitialized values that might change when the resource finishes loading. Therefore, it is always advisable to wait until the resource has finished loading before accessing its properties. However, many times, especially while prototyping, you may want to change a property value before the resource is loaded without regard for its proper initialized value. For instance, you may want to change the scale visibility of a layer or the initial viewpoint of a map. To simplify this workflow without requiring that the resource first be loaded, loadable resources permit overriding their properties before the resource has finished loading and the overridden value will take precedence over the value specified in the resource's metadata.
The following code example shows how you can override the min/max scale properties of a map without having to load it first.
// Create a map with the streets basemap style.
ArcGISMap map = new ArcGISMap(BasemapStyle.ARCGIS_STREETS);
// Set the scale at which this map can be viewed.
map.setMinScale(8000);
map.setMaxScale(2000);
map.loadAsync();
map.addDoneLoadingListener(() -> {
// Overridden min & max scale values will be retained even when the resource finishes loading.
System.out.println("Map Status: " + map.getLoadStatus());
System.out.println("Min Scale: " + map.getMinScale() + " Max Scale: " + map.getMaxScale());
});