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

Remove override file #57

Open
etj opened this issue Sep 29, 2015 · 1 comment
Open

Remove override file #57

etj opened this issue Sep 29, 2015 · 1 comment

Comments

@etj
Copy link
Member

etj commented Sep 29, 2015

The file

geofence/WEB-INF/classes/geofence-datasource-ovr.properties

prevents user override file to be used, and should be removed.

The issue is both in

@etj
Copy link
Member Author

etj commented Jan 18, 2017

In general, users should define their own override file: see https://github.com/geosolutions-it/geofence/wiki/GeoFence-configuration#providing-a-configuration-file for details.

The persistencemodule defines an overrider which loads the file classpath*:geofence-datasource-ovr.properties. This definition is used in almost every geofence module, where a file geofence-datasource-ovr.properties is located in the test/resources directory.
The web module anyway inherits this overrider, and any geofence-datasource-ovr.properties file will be loaded, leading to potential race conditions. Internal usage of this ovr configuration only provides one such file at any time.

Please note that the user-defined ovr file will have higher priority wrt to the geofence-datasource-ovr.properties, that should only be used for internal purposes.

Anyway, in order to have less configuration files around, distributing an internal fixed ovr file should be avoided. Probably the best way to deal with default values should be setting them into the properties field in the overrider definition inside the applicationContext.xml file.

afabiani pushed a commit that referenced this issue Oct 2, 2018
 - rollback persistence change due to ISSUE #57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant