Closed ghost closed 12 years ago
Hi PaulZH,
The steps to have the browser run against BBC music or DBpedia is to replace the configuration.json and facets.json files with the ones under the other-config folder i.e. the copied files need to be renamed.
In case you are already doing so, it might be caused by the relatively expensive query that is currently used to fetch resources which is : SELECT ?x ?p ?o WHERE { ?x ?p ?o. ?x a < http://dbpedia.org/ontology/Artist>} LIMIT 10 this is captured at: https://github.com/fadmaa/RDF-faceted-browser/issues/3
please give it a try and let me know... you might also want to try the provided DBpedia countries example
The steps to have the browser run against BBC music or DBpedia is to replace the configuration.json and facets.json files with the ones under the other-config folder i.e. the copied files need to be renamed.
Done in this way.
you might also want to try the provided DBpedia countries example
Will do and let you know.
Hi,
I discovered that the issue potentially has to do with the version of Tomcat used. I reinstalled everything on another machine running Tomcat 6 where it works as expected.
The initial 'never ending' installation was on a Tomcat 7.
Paul
Thanks for reporting. I only tested it on Tomcat 6. I will check what goes wrong when using Tomcat 7
Thanks,
there was a bug in the way the configuration files are read. should be fixed! feel free to re-open if it is not fixed
Hi,
Using the environment with the supplied bbc settings (as they are) as configuration.json and facets.json. When opening the app, I get a 'working' page forever.
Doing the query (SELECT ?x WHERE {?x a http://dbpedia.org/ontology/Artist .}) from a REST client environment, returns results in an acceptable timeframe.
What am I missing?
Paul