See: Description
| Interface | Description |
|---|---|
| Store |
Store is the main interface for operations on OSLC Resources with the backing
triplestore.
|
| Class | Description |
|---|---|
| StoreFactory |
Provides factory methods to instantiate concrete implementations of
Store that keep the
triplestore information in various ways (RAM, disk, over the network). |
| Exception | Description |
|---|---|
| ModelUnmarshallingException |
ModelUnmarshallingException is an exception that occurs during
Model
transformation. |
| StoreAccessException |
StoreAccessException is an exception for read/write problems with the backing triplestore or
dataset.
|
Lyo Store is a library that can be used to persistently store OSLC resources in a triplestore. This can be useful to cache the results of REST resource requests for a faster retrieval of resources upon subsequent requests. Alternatively, a lifecycle tool may choose to preload its OSLC resources in the triplestore, allowing its OSLC server to provide OSLC services that interact directly with the artefacts consistently and conveniently managed using the expected RDF technologies. This, for example, makes it relatively easier for an OSLC server to provide clients with a TRS provider, or a SPARQL-endpoint for more advanced query capabilities.
The Store expects the OSLC resources to be instances of
IResource subclasses, with
appropriate OSLC annotations. Such subclasses can be defined manually. Better still, you can
use Lyo Toolchain to graphically model the domain and automatically generate OSLC4J-compliant
Java code.
The main entry point of this library is the Store
interface. Three concrete store implementations are provided allowing for in-memory, on-disk
and a SPARQL-compatible Store implementation. You can instantiate any of these concrete
implementations using the StoreFactory class.
Copyright © 2018. All rights reserved.