Examples of org.geotools.data.store.ContentDataStore

• org.geotools.data.store.ContentDataStore
  Abstract base class for data stores.

  A datastore contains a set of entries ( {@link ContentEntry}). Each entry corresponds to a "real world dataset". For instance, a shapefile datastore would contain a single entry which would represent the shapefile on disk. A postgis datastore could contain many entries, one for each table in the database.

  Each entry is identified by a name ( {@link Name}). The name can be qualified with a namespace uri, or unqualified (in which the namespace uri is null). An example of a datastore that might use qualified names is WFS, where in each entry corresponds to a WFS "Feature Type", which have namespace qualified name. Other datastores (such as databases) use unqualified names.

  When entry names of a datastore are unqualified, a default namespace uri can be set "globally" on the datastore itself, see {@link #setNamespaceURI(String)}. When this value is set, unqualified entry names are implicitly qualified with the global namespace uri.

  Subclasses

  At a minimum subclasses must implement the following methods:

  • {@link #createTypeNames()}
  • {@link #createFeatureSource(ContentEntry)}

  The following methods may also be overriden:

  • {@link #createContentState(ContentEntry)}

  The following methods may be overriden but only to narrow the return type to a specific subclass of {@link ContentFeatureSource}.

  • {@link #getFeatureSource(String)}
  • {@link #getFeatureSource(String,Transaction)}
  • {@link #getFeatureSource(Name,Transaction)}

  @author Jody Garnett, Refractions Research Inc. @author Justin Deoliveira, The Open Planning Project @author Niels Charlier @source $URL$

Related Classes of org.geotools.data.store.ContentDataStore