Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuration #69

Closed
GoogleCodeExporter opened this issue Sep 10, 2015 · 5 comments
Closed

Configuration #69

GoogleCodeExporter opened this issue Sep 10, 2015 · 5 comments

Comments

@GoogleCodeExporter
Copy link

(1) Simplify configuration by only using dedicated configuration files (i.e., 
the cumulusRDF.yaml). Remove the CumulusRDF configuration from web.xml.

(2) Add new configuration parameters for dictionary configuration (as discussed 
on the [ConfCall2 2. conference call])  


Original issue reported on code.google.com by andreas.josef.wagner on 4 May 2014 at 1:52

@GoogleCodeExporter
Copy link
Author

Original comment by andreas.josef.wagner on 4 May 2014 at 1:53

  • Added labels: v1.1.0

@GoogleCodeExporter
Copy link
Author

Original comment by a.gazzarini@gmail.com on 6 May 2014 at 3:08

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author


Original comment by a.gazzarini@gmail.com on 6 May 2014 at 10:21

@GoogleCodeExporter
Copy link
Author

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

@GoogleCodeExporter
Copy link
Author

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

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant