org.autoplot.fdc.FedCatSourceFactory

Generates data sources based off URIs of the form: vap+dfc:LOCATION

FedCatSourceFactory( )

getCompletions

getCompletions( org.autoplot.datasource.CompletionContext cc, ProgressMonitor mon ) → java.util.List

Parameters

cc - a CompletionContext
mon - a ProgressMonitor

Returns:

java.util.List

[search for examples] [view on GitHub] [view on old javadoc]

getDataSource

getDataSource( java.net.URI uri ) → org.autoplot.datasource.DataSource

Break a catalog URI down into parts Federated Catalog Paths are very different from many Autoplot URIs, provide parsing for these.

Parameters

uri - an URI

Returns:

A Map that always has the following keys: "handler" - Should always be 'vap+dc' "rootUrl" - The URL to the root node, will often be null, meaning that the URLs must be found in the global catalog "path" - The sub path of interest offset from the root URL "params" - The query parameters. Will be null for default datasets

[search for examples] [view on GitHub] [view on old javadoc]

isFileResource

isFileResource( ) → boolean

Returns:

boolean

[search for examples] [view on GitHub] [view on old javadoc]

reject

reject( String sUrl, java.util.List lProblems, ProgressMonitor mon ) → boolean

We have to reject the URI in order to pop up the inspection dialog box. This makes sense because if the URI is good, folks just want to see the data.

Parameters

sUrl - a String
lProblems - a java.util.List
mon - a ProgressMonitor

Returns:

a boolean

[search for examples] [view on GitHub] [view on old javadoc]

supportsDiscovery

supportsDiscovery( ) → boolean

This data source is pretty much only discovery, so of course we return true here.

Returns:

true

[search for examples] [view on GitHub] [view on old javadoc]