Difference between revisions of "SDI Library"
| Line 10: | Line 10: | ||
''SDI Library'' exposes basic gCube clients towards [[[SDI-Service]]] REST interfaces. | ''SDI Library'' exposes basic gCube clients towards [[[SDI-Service]]] REST interfaces. | ||
''SDI Library'' also exposes means to dynamically load and instantiate client implementations for specific SDI subsystems (e.g. GeoServer, GeoNetwork). | ''SDI Library'' also exposes means to dynamically load and instantiate client implementations for specific SDI subsystems (e.g. GeoServer, GeoNetwork). | ||
| − | |||
=== Philosophy=== | === Philosophy=== | ||
The library has been designed to maximize isolation of dependencies : common complex logic is supported on services and client implementations are discovered at runtime. | The library has been designed to maximize isolation of dependencies : common complex logic is supported on services and client implementations are discovered at runtime. | ||
| + | |||
| + | |||
| + | == Static Clients == | ||
| + | === SDI Management === | ||
| + | |||
| + | == Dynamic Clients == | ||
| + | === GeoServer === | ||
| + | === GeoNetwork === | ||
| + | |||
| + | == Use Cases == | ||
| + | === Migrating from legacy GIS - Interface === | ||
| + | === Migrating from legacy Geonetwork library === | ||
Revision as of 16:51, 22 February 2021
SDI Library is a java library designed to help developers interact with gCube SDI. It offers clients implementations towards the SDI subsystems (i.e. SDI-Service, GeoNetwork, GeoServer ).
Contents
Design
Following diagram illustrate the relations between the various clients components in gcube-sdi-suite.
To external users, the main component of interest is sdi-library, built on top of the sdi-interface which contains common classes definition.
SDI Library exposes basic gCube clients towards [[[SDI-Service]]] REST interfaces.
SDI Library also exposes means to dynamically load and instantiate client implementations for specific SDI subsystems (e.g. GeoServer, GeoNetwork).
Philosophy
The library has been designed to maximize isolation of dependencies : common complex logic is supported on services and client implementations are discovered at runtime.
