Closed GoogleCodeExporter closed 8 years ago
Original comment by andreas.josef.wagner
on 4 May 2014 at 1:53
Original comment by a.gazzarini@gmail.com
on 6 May 2014 at 3:08
Original comment by a.gazzarini@gmail.com
on 6 May 2014 at 10:21
CumulusRDF, regardless the "kind" of instance (standalone, embedded, web
module) will use these subsequent strategies for finding a valid configuration:
• looks for a system property "crdf.config.file" which indicates a valid and
readable configuration file;
• looks for a system property "cdrf.config.dir", which indicates a valid and
readabale directory where there must be a file "cumulusRDF.yaml"
• looks for a classpath resource /cumulusRDF.yaml.
• load the embedded (default) classpath resource /cumulusRDF-default.yaml
If one of the strategy fails (e.g. file not found, directory not readable,
resource not found) then the next stratgy will be used, until a valid
configuration is found.
Original comment by a.gazzarini@gmail.com
on 7 May 2014 at 9:30
I'm closing this issue because is basically completed. As additional notes to
the requirements above,
- the package where is located the default configuration will contain also one
sample configuration file for each kind of supported storage (at the moment C*
1.2.x and C* 2.x)
- the default configuration file will contain a section for each kind of
supported storage. The appropriate set of attributes will be picked up by
CumulusRDF at runtime (depending on the plugged storage module).
AG
Original comment by a.gazzarini@gmail.com
on 12 May 2014 at 5:00
Original issue reported on code.google.com by
andreas.josef.wagner
on 4 May 2014 at 1:52