Hi Walter,

you are perfectly right, the file
   geofence/WEB-INF/classes/geofence-datasource-ovr.properties
shouldn't be there at all. Default values should be fine, and the override file
should only be used for externalizing the configuration.

Issue https://github.com/geoserver/geofence/issues/57

   Thanks,
   Emanuele

Alle 14:11:42 di Monday 28 September 2015, Walter Stovall ha scritto:
> Thanks – it may be a few days before I can upgrade to 2.8 but I will indeed
> get to that soon.
> 
> I did find a workaround for my problem.  Seems like there’s definitely a
> bug in the handling of the property-override file.  I used procmon to
> verify that geofence is indeed reading from my property override file.  In
> that file I have this:
> geofenceDataSource.url=jdbc:h2:c:/fdotwebsvc/h2db/geofence
> 
> That line is ineffective, as geofence still creates the file at its default
> location.  So I modified the file at
> geofence/WEB-INF/classes/geofence-datasource-ovr.properties.
> 
> There, I changed this line that creates the h2db in the tomcat directory:
> geofenceDataSource.url=jdbc:h2:geofence_db/geofence
> 
> I set it the same as the ineffective setting in my property override file. 
> Now it works correctly.
> 
> From: Jody Garnett [mailto:[email protected]]
> Sent: Sunday, September 27, 2015 5:28 PM
> To: Walter Stovall
> Cc: [email protected]
> Subject: Re: [Geoserver-users] Unable to create geofence h2 database under
> Linux
> 
> I have not tried GeoFence on 2.7.x yet ... but a lot of work has been done
> a community module for 2.8 (including REST API and a new integrated GUI).
> 
> If you are in position to test please give it a go - feedback / testing /
> encouragement for the developers involved is always a good thing.
> 
> 
> 
> --
> Jody Garnett
> 
> On 25 September 2015 at 05:24, Walter Stovall
> <[email protected]<mailto:[email protected]>> wrote: Using
> GeoServer 2.7.2 and the matching download of GeoFence.  On my local
> Windows computer geofence starts up and creates its h2 (default) database
> by default at the home directory of my tomcat instance.  That’s OK under
> Windows but not Linux.
> 
> I tried creating a property override file so I can change the location
> where the h2 database gets created but I’m having no luck getting it to
> happen there in spite of confirming in the tomcat log that my property
> file is being read.
> 
> In the JVM startup flags I have:
> -Dgeofence-ovr=file:/C:\fdotwebsvc\GeoServerDataDir\geofence-byers-ovr.prop
> erties
> 
> During tomcat startup I observe this in the log:
> 12:17:12,047  INFO PropertyOverrideConfigurer:177 - Loading properties file
> from URL
> [file:/C:/fdotwebsvc/GeoServerDataDir/geofence-byers-ovr.properties]
> 
> In the geofence-byers-ovr.properties file I have a single line with:
> geofenceDataSource.url=jdbc:h2:C:\fdotwebsvc\h2db\geofence.h2.db
> 
> But when I start my local tomcat I see nothing get created in the above
> h2db directory and I see a lock-file added to the
> {tomcat-home}/geofence_db directory.
> 
> What can I do to change the location where the db gets created?
> 
> Thanks for any assistance!
> 
> Walter
> 
> ---------------------------------------------------------------------------
> ---
> 
> _______________________________________________
> Geoserver-users mailing list
> [email protected]<mailto:[email protected]
> rge.net> https://lists.sourceforge.net/lists/listinfo/geoserver-users


-- 
==
GeoServer Professional Services from the experts! 
Visit http://goo.gl/NWWaa2 for more information.
==

Ing. Emanuele Tajariol
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:    +39 0584 1660272
mob:   +39  380 2116282 

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

------------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to