D-Net

ignore integration test

Looks like using UNION is much more performant than using OPTIONAL. See http://www.snee.com/bobdc.blog/2014/10/dropping-optional-blocks-from.html

Test adapted to previous commit

Ignore tests that require a running virtuoso on localhost

Added @RunWith(JUnit4.class)

Added @RunWith(JUnit4.class)

Added @RunWith(JUnit4.class)

Deleted wrong RIOT writer

Cleanup after creating resources

fixed test

Annotation for tests

test to ensure the sparql template are well formed and once instantiated they are correctly processed by virtuoso

No need dedicated resource file in test to test the template loading

test

Registering providers as catalogue groups

Debugging "org.apache.jena.riot.RiotNotFoundException: Not found" and related(?) parsing issue

I think we must use an InfModel to process the rdf before registering it

Because of https://support.d4science.org/issues/11466, let's not throw exception, but let's try to continue, if possible.
Purge method implemented and tested

without testing a woman can die

Debugging for unexpected NPE

Testing RecordParserHelper

Extract the rdf block from the record submitted for registration

Can't use jena Query because does not support inference rule, can't use jena HttpEngine because it does not support long queryif we do not use Query: hence let's query with handmade post request to the sparql endpoint.

testing template loading

Fixed compilation for test

Fixed expected value

Testing the registry library

ByPass QueryBuilder, otherwise the virtuoso pragma are not parsable

Playing with inference rules on the remote sparql endpoint

throws exception

Refactoring and deprecation for registration on catalogue and registry

testing

Updated test

Testing RDF XML serialization

API that read from Virtuoso

Testing Virtuoso DESCRIBE remote queries.

Creating json for the CKAN Catalogue

Fixed after refactoring classes

test

Sleep to make the test work with async controller

Test for illegal chars

Fixed virtuoso drop and added test

Ignoring old test to be revised

feeding the registry with resources and relationships

More mapping to gcube resources and facets

Refactoring

First mapping for services and tests

Playing with Jena API

Ignore test as it requires a running virtuoso server

API for storing on virtuoso

keep playing with virtuoso

JobNodes to work with Virtuoso

VirtuosoClient and some tests assuming there is a local virtuoso server (hence ignored)

First tests with Virtuoso.

project structure