New issue 303 by sander.v...@oucs.ox.ac.uk: Setting 'simal.repository.dir'
for database path does not match Joseki settings
http://code.google.com/p/simal/issues/detail?id=303
There is a setting 'simal.repository.dir' for determining the directory
where the Jena database is stored on disk. If this setting is not used, the
database will be stored in a subdirectory of the 'current dir' when the
application was started.
However, setting this property does not affect the Joseki SPARQL settings.
This means that if, say, you use the following startup param:
-Dsimal.repository.dir=/opt/simal/data
The database will be loaded from that directory, but if the application is
started from another directory Joseki will initialise a separate database
from the current directory and query from there.
Impact
This leads to no results being found when SPARQL querying the database
Workaround
You can create a symlink from the path used by Joseki to the correct path.
(Path to) Solution
The file 'joseki-config.ttl' contains the definition of the datasets, but
will have to be possible to override these settings at runtime.
Comment #1 on issue 303 by sander.v...@gmail.com:
Setting 'simal.repository.dir' for database path does not match Joseki
settings
http://code.google.com/p/simal/issues/detail?id=303
With the changes in the way the location of the database is determined
(using SIMAL_HOME and user.home) the chances of this issue happening is
significantly increased and will likely occur out-of-the-box.
According to the docs [1] it's possible to specify the dataset in the
request.
Comment #2 on issue 303 by sander.v...@oucs.ox.ac.uk:
Setting 'simal.repository.dir' for database path does not match Joseki
settings
http://code.google.com/p/simal/issues/detail?id=303
This issue was closed by revision r2235.