| Modifier and Type | Method and Description |
|---|---|
ContentTripleSource |
ApplicationImpl.getContentTripleSource() |
| Modifier and Type | Method and Description |
|---|---|
void |
ApplicationImpl.setContentTripleSource(ContentTripleSource source) |
| Modifier and Type | Method and Description |
|---|---|
ContentTripleSource |
Application.getContentTripleSource() |
| Constructor and Description |
|---|
BasicCombinedTripleSource(ContentTripleSource contentSource,
ConfigurationTripleSource configurationSource) |
| Modifier and Type | Class and Description |
|---|---|
class |
ContentTripleSourceSDB
Create the connection to the SDB triple-store.
|
| Modifier and Type | Class and Description |
|---|---|
class |
ContentTripleSourceSPARQL
For a SPARQL endpoint, each connection is created as needed by the
RDFService, so there is no need to manage connections here.
|
| Modifier and Type | Class and Description |
|---|---|
class |
ContentTripleSourceTDB
A TDB triple-store has no concept of connections, so we need not manage them
here.
|
| Modifier and Type | Class and Description |
|---|---|
class |
ContentTripleSourceVirtuoso
So far, it's just like a ContentTripleSourceSPARQL but it uses an instance of
RDFServiceVirtuoso.
|
Copyright © 2016. All rights reserved.